After homing X and Y, can I auto move to a non 0,0 location?

More
1 year 6 months ago #326803 by pgf
Okay, I think a picture will help.

Homing on 0 works, as in the upper diagram.  But it leaves the bed far from me.  In the title of the thread, I asked whether there's a way to automatically move after homing, so that I end up as in the lower diagram.  I haven't yet tested whether simply setting "HOME" to 12, rather than 0, would accomplish this.  That's because since homing (and even rapids, on my mill) are very slow, I'd really rather skip the extra bed travel, and have it home directly to 12, and stayed there.



 

Please Log in or Create an account to join the conversation.

More
1 year 6 months ago #326805 by spumco
OP-

Thank you, that helps.

Would you like the table to be as close to the operator as possible (max Y) as well as centered on X when the homing routine is complete?  This is how I've configured my moving-table mill.

Please Log in or Create an account to join the conversation.

More
1 year 6 months ago #326806 by pgf
That would be great -- but I'd also be happy with simply max-X and max-Y.

Please Log in or Create an account to join the conversation.

More
1 year 6 months ago #326815 by pgf
I've now tested my original homing-at-0 config, with HOME=12, and it does indeed home as usual, and then set the current position to 12. So the question asked in the thread title is answered.

I'd still like to home-at-12, instead.

Please Log in or Create an account to join the conversation.

More
1 year 6 months ago #326823 by spumco

I've now tested my original homing-at-0 config, with HOME=12, and it does indeed home as usual, and then set the current position to 12. So the question asked in the thread title is answered.

I'd still like to home-at-12, instead.
 
If you'd like the table to home all the way to the operator's left (X-max), and your two X limit switches are on the same input, you can change your INI config so that the search direction is positive. I think the following is what you want:

MIN_LIMIT = -0.001
MAX_LIMIT = 12.001
HOME_IS_SHARED = 1
HOME = 12
HOME_OFFSET = 12 
HOME_SEARCH_VEL = .2
HOME_LATCH_VEL = -0.015
HOME_FINAL_VEL = 0
HOME_USE_INDEX = NO
HOME_IGNORE_LIMITS = YES
HOME_SEQUENCE = 2

This will result in an X homing sequence as such:
  • Table moves left (searching X-pos) at speed 0.2
  • Limit switch reached
  • Table moves right (X-neg) until limit switch clears at speed 0.015
  • Table stops, homing complete, DRO will be set to "12"
The reason for the "12.001" MAX_LIMIT value is that if you set it the same as HOME, then when you are finished homing the axis will be on the max soft limit.

If you would like the table to finish the sequence in the middle of travel, you can change the above as follows:

HOME = 6
HOME_FINAL_VEL = -.2

Same behavior as above, except after the limit switch is cleared the table will move right (X-neg) to the middle of travel and stop with the DRO at "6"

Similar edits can be made to the Y-axis to have the table finish close to the operator.
The following user(s) said Thank You: pgf

Please Log in or Create an account to join the conversation.

More
1 year 6 months ago #326825 by pgf
Thanks for thinking so hard about this. I appreciate it.

Two things: first, because of how my switches are set up, I believe both HOME_SEARCH_VEL and HOME_LATCH_VEL need to be positive. The backoff movement is added automatically in between them. Second, HOME_FINAL_VEL isn't a signed velocity. I realized that yesterday while trying various combinations. It would probably be better if the homing code threw an error, since it implies a slight misunderstanding of the config, but instead it seems to simply use abs(HOME_FINAL_VAL).

In the end, the difference between what you propose and what I tried yesterday is the value of HOME_OFFSET. That could well make the difference. I'll try it later today.

Thanks again!

Please Log in or Create an account to join the conversation.

Time to create page: 0.054 seconds
Powered by Kunena Forum