-
Notifications
You must be signed in to change notification settings - Fork 36
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
gsender 1.3.10 EDGE disconnect/reconnect required upon Home in Z-limit if machine is not unlocked. #451
Comments
The problem condition does not appear to occur if the Z-axis is already in the Z-limit when the application is first started up. In other words, if the application is stopped and restarted with the axis in the Z-limit, upon restarting the application, the Click to Unlock Machine does not appear to work and it is necessary to click the Home button to home the machine and continue working. However, it does appear that the symptoms may differ if the Z-axis is driven back into the limit and the procedure is attempted. In this case, Disconnected appears rather than Homing, and it is necessary to use the disconnect/connect process to return to normal function. |
To replicate:
At this point, it appears that the easiest way to get out of this condition is to disconnect from the machine and then reconnect to it though one can also stop and restart the application. The subsequent homing operation is successful.
This is sub-optimal behavior (a bug). Avoiding this condition is suggested. The solution appears to be as simple as greying out the home button until after Click to Unlock Machine is clicked. If the Click to Unlock Machine button is pressed before clicking the Home button, the homing operation proceeds normally.
The text was updated successfully, but these errors were encountered: