I'm using master that I down loaded about  10 days ago with Gmoccapy that came with it. I was controlling my mill just using the jog buttons and chose not to send commands using MDI mode. This machining work required the jog button to be pushed for minutes at a time and then released when the desired axis travel was completed.

On a number of occasions I had to push the machines emergency stop button to stop the jog since releasing the jog button did absolutely nothing. Most of my movements were slow less that 3 inches per minute in the X axis with a travel range of about 11 inches so this took a considerable amount of time. Most of the time jog stopped as expected but not all the time and came close to breaking to installed cutting tool.

I'm thinking that this may be related to status not seeing that jog button was released or that status for that particular button froze in some way, perhaps even by some sort of time out. I failed to see if the button in Gmoccapy changed color from yellow to white or not when the button was released. I think the code used for manual jogging and its related status info may need a review to see if there is something being overlooked that could be time related.

I do not have any time to look into this further now but this occurred perhaps 8 times in the last several days using this particular manual jogging machining method.





_______________________________________________
Emc-developers mailing list
Emc-developers@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/emc-developers

Reply via email to