-
-
Notifications
You must be signed in to change notification settings - Fork 19.3k
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
[FR] During G28, go to X0 before homing Y, G29 should respect min positions #17270
Comments
See if this helps: #define HOMING_BACKOFF_MM { 11, 2, 2 } |
You should try to set HOMING_BACKOFF_MM to 11 for X axis edit: @thinkyhead same time - same station |
@rado79 — The proper canned reply is in Markdown and contains hyperlinks. Since the issue is resolved there's no need to refer the user to other forums for further help. |
Has anyone reported that |
Also, G29 doesn't respect X_MIN_POS either. |
Whenever there are homing or leveling issues, we now ask everyone to follow a standard procedure to gather more information so that we're not just taking stabs in the dark. Here is the boilerplate:
Repeat this procedure, if needed, to demonstrate inconsistencies. From these logs we should hopefully get a better idea of what's going on with your machine. |
@JoshWelsh try with latest bugfix-2.0.x. Last night changes have been made for homing backoff with core kinematics. |
I think it is not skipping homing the second axis, but performing a false positive on the TMC sensor. Please check this for a possible solution. Basically it is just a delay after homing the first axis. |
Apologies for the delay, and honestly I very much appreciate the effort everyone puts in to this product, so thank you! if this turns out to be a config issue on my side, I'm happy to be the guy that stands up and says "my bad, I'm an idiot." That said, the travel moves are clearly going to off-limits region in Log Output
|
@thinkyhead curious if you had thoughts on this yet? Would very much like if G29 stayed in bounds.. |
Is this thing on? |
If you need to home x before y - how about
|
Hi, how does this address let alone solve the issue of G29 not respecting minimum positions? |
I've been under a pile of issues and trying to steal time to fix some things and work on the release. Did you figure out your issue yet? From a casual reading of your log, it looks like you configured the mesh to start at X = -11 and maybe not with a usable mesh inset within the bed. Please test the |
I can confirm that with the latest version 2.0.6.1, G29 still does not respect head min positions. log is attached it is visible from the log that in my case first G29 point is at X25.00 Y-20.00. my head min positions are as follows
my NOZZLE_TO_PROBE_OFFSET is -15, 64, -5.15 my PROBING_MARGIN is set to 10 so, if I understand correctly how this should work, my first G29 point should be ABS(X_MIN_POS) + PROBING_MARGIN, ABS(Y_MIN_POS) + PROBING_MARGIN. In my case that would be X11 Y30 on the head or maybe better to say PROBING_MARGIN should be PROBING_MARGIN + ABS(XY_MIN_POS). That way it would be in relation with PROBING_MARGIN_FRONT from advanced configuration thx for the hard work to all! |
setting PROBING_MARGIN_FRONT in advanced configuration can fix this but I still think G29 should respect min positions |
@gec100 it should already be respected. Post your configuration files and maybe that can help spot a problem. |
@sjasonsmith here they are :) |
Description
Using my HEVO with sensorless homing, I have "X_MIN_POS" set to "-11" and I would like the homing of X to complete only after the extruder is moved back to X=0. Currently when the printer homes X, it sets X=-11 and then homes Y, which causes collision between my part cooling fan ducting and some hard parts for the Z axis linear rods.
Basically, go to X=0 before doing anything else in G28.
Feature Workflow
Additional Information
Hopefully this all makes sense and is simple, but I can provide pics if needed.
The text was updated successfully, but these errors were encountered: