|
|
Post by brysny on May 17, 2012 13:39:14 GMT -8
I am running MSM beta 1.3.12, demo license, on XP, mach .062 and only a shuttle pro plugin.
If I ref-all, run a program, it comes to a tool change, switches screens, but then if I try and stop the code (ie only wanted to run the first tool, or realize that tool is not available, or need to set TLO, etc) MSM pops up an error box that tool change was aborted and also triggers a system reset. Since I have a stepper setup, and mediocre home switches, that means I just lost position. Arg. Is this an intended function? How do I stop a program cleanly at a tool change?
|
|
|
|
Post by DaveCVI on May 17, 2012 18:30:51 GMT -8
Hum, it's a "semi-intended" function....  I understand the point you're making. MSM does tend to get insistent about a reset when a tool change sequence is aborted. I'll not say that it can't be different, but I do have to think about it as there are multiple reasons a tool change can get interrupted. Some are less serious than others, and I'll need to study the code to see what flexibility there is re this request (sometimes this happens as the result of an error trap where we don't know what happened, and then the only safe thing is a full reset and refusal to go on). It has not been an issue prior to this - but I have thought of it before and just never got around to looking into the details. I have a couple of questions so that I can understand your usage pattern better: For most of a tool change there is no movement happening (other than when MSM is going to the TCP etc). So, I'd not have thought that the reset would result in lost steps for the steppers. What is the situation that causes the lost steps? What are you doing to stop the tool change? what key or button? esc key, stop button or? Dave |
|
|
|
Post by brysny on May 18, 2012 8:58:40 GMT -8
The steppers lose position because I have the reset wired up more as an e-stop function. So even if the table doesn't move, the stepper controller disables and it when turned back on it goes to the nearest full step instead of the previous microstep position.
I think I can rewire and leave the spindle hard disable tied to the Reset and leave the steppers powered to fix the issue.
I did not realize 'Esc' key does anything, but I tried that and while it leaves buttons flashing as if it was still in a toolchange, it does stop the program without a Reset. I had been using the Stop key because feedhold didn't do anything.
|
|
|
|
Post by DaveCVI on May 18, 2012 11:05:48 GMT -8
Hi, I did not realize 'Esc' key does anything, but I tried that and while it leaves buttons flashing as if it was still in a toolchange, it does stop the program without a Reset. Yeah, this is a mach thing - esc aborts the current operation. The problem is that it also aborts the current script that is being executed - this stops the script MSM is running, but it leaves things in an inconsistent state (the LEDs stay flashing as the script never gets to turn them off as it never finishes). I had been using the Stop key because feedhold didn't do anything. I think I can fix the specific issue of the stop key doing a reset during a tool change - let me give it a shot. The feed hold does nothing as it "holds" feed moves - and there is no feed move being executed during a tool change - so it does nothing. Dave |
|
|
|
Post by DaveCVI on May 18, 2012 12:29:30 GMT -8
Please DL MSM 1.3.14 beta - it has a change to the stop button so it no longer forces a reset if used during a tool change.
Dave
|
|
|
|
Post by brysny on May 18, 2012 16:48:52 GMT -8
Awesome. That is some great customer service.
Thanks!
|
|
|
|
Post by DaveCVI on May 18, 2012 22:21:44 GMT -8
 Dave
|
|
