How to jog when beyond soft limits

More
1 year 4 months ago - 1 year 4 months ago #330463 by Lcvette
are you on the soft limit or the hard limit? if the hard limit, then set a home offset so you have a bit of cushion for drift on power cycling. if its a hard limit switch, in probe basic in the side bar tab for "WCS" there is a button for LIIMITS OVERRIDE. this should ignore the limit switch and allow you to jog away. but this isn't really going to fix the issue over all. you should set the home offset with enough distance away from the limit towards the useable axis travel side so it doesn't ever encounter this situation.
Last edit: 1 year 4 months ago by Lcvette.
The following user(s) said Thank You: tommylight

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

More
1 year 4 months ago #330483 by kubes
This is just soft-limits as I am using absolute encoders and while I "home" it only sets the axis as homed, there is no travel or switches involved. I may add hard-limit but that is really more of a belts and suspenders solution.

I am not understanding how HOME_OFFSET will fix this for soft-limits. My understanding of HOME_OFFSET my be wrong. but it will offset the home and then the soft-limits will be offset, but I can still jog right to them, and my "little over error" will still be an issue.

Does the LIIMITS OVERRIDES only there for hard limits or will also work for soft-limits?

This all can be just me and my very limited understanding of how to correctly set-up high resolution absolute encores and soft-limits.

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

More
1 year 4 months ago - 1 year 4 months ago #330489 by Kieran
On my AXIS gui setup, I can switch to "joint mode" by hitting $ (shift-4)
which lets the servos jog slowly back into the normal travel range. Hit $ again to go back to "world mode" to run as normal from there. Im guessing the other GUI have an easy way to get into joint mode as well. you could also manually turn the ballscrew a little :D
Last edit: 1 year 4 months ago by Kieran.
The following user(s) said Thank You: tommylight

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

More
1 year 4 months ago #330493 by pippin88
I can see you issue and agree that a better solution is needed for absolute encoder setups.

Maybe two sets of software limits are needed?
Working area
Absolute maximum travel
If machine is within "working area" travel/jogging outside is needed
If machine is outside "working area" but within "absolute maximum travel", then allow jogging. Once within "working area" don't allow jogging/movement back out

Work around:
Move machine off soft limits on shut-down
forum.linuxcnc.org/49-basic-configuratio...tion-shutdown#226443
The following user(s) said Thank You: tommylight

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

More
1 year 4 months ago - 1 year 4 months ago #330502 by rodw
Limit switches should never be hit so need to be outside the working area. If you use use shared home/limit switches, a home_offset in the inI file should be used to move the axis away from the limit switch during homing, Your home_offsets are set to 0
Last edit: 1 year 4 months ago by rodw.

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

More
1 year 4 months ago - 1 year 4 months ago #330516 by kubes
@pippin88, Thanks for the move on the shutdown workaround! It will help with the symptom.

Thinking about this more and doing some more testing. Adding more limits will not address the root issue, as any we could be at that new limit and this could still exceed it.

I believe it's a limit resolution issue. Note, I do not know how the code works in comparing and testing for limits. I should be able to specify the resolution of the comparison. In the current case it looks like is doing the comparison at 10ths (.0001) and that scale is just too small. One should be able to set limits at the granularity required for their hardware. My max machine limit is 0.3 absolute in this case. I tried changing my limits to 0.3, 0.30, 0.300, etc. But is seem to compare .3 to the current position of 0.3007 (example). Again, in my case, the axis can shift by 0.0005 +/- .0002. So I would like my limit to be 0.300 (truncated (not rounded) at thou) thus 0.3007 would not be beyond the limit. Think 0.30007 > 3.000 vs 0.300 > 0.300.  Another means would be to add a VARIANCE ini setting to use to calculate the amount of variability in the limit comparison.

Also, this could be a issue for anyone with limits, but maybe due to off_set on the hard limit people don't see it. Or I am completely wrong in my limited understanding of limits work....

In addition, I am more sure the JOINT vs AXIS limit works as documented. (more on that later)
Last edit: 1 year 4 months ago by kubes.

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

Time to create page: 0.059 seconds
Powered by Kunena Forum