FabMo
After hitting an endstop with a manual move, the manual controls appear to be locked out for a short period of time
If intentional, this really wants some kind of user notification.
But it feels....weird. After I hit an endstop when moving in 0.001in increments, what I want to do is to back of 0.001 inch and I can't, unless I wait for a bit.
I just tested this on the Desktop MAX we have in house. I checked it in .1" increments and .001" increments and was able to jog into the end stop then away from it without issue (maybe 1/2 second delay, hard to even estimate how long it was). Could you characterize the issue further so that I can attempt to replicate it?
Ted says that often in the era of handibot, you can lose connection with running into a wall. But maybe it's this is related. Apparently it is an intermittent problem. The handibot did not have a limit switch, so every limit was running into the end stop. sometimes it was less than 1 in 40.
I’ll see if I can repro and if I can, I’ll take a video.
On Jun 7, 2022, at 11:48 AM, Rob Mackie @.***> wrote:
Ted says that often in the era of handibot, you can lose connection with running into a wall. But maybe it's this is related. Apparently it is an intermittent problem. The handibot did not have a limit switch, so every limit was running into the end stop. sometimes it was less than 1 in 40.
— Reply to this email directly, view it on GitHub, or unsubscribe. You are receiving this because you authored the thread.
I'm unable to repro this today, despite repeated attempts to do so. Happy to update when/if I can trigger it again.