Machsupport Forum
Mach Discussion => General Mach Discussion => Topic started by: miket161 on October 14, 2011, 03:27:57 AM
-
Hello,
Every once in a long while I get a limit switch error while cutting. Or I press the e-stop button.
What would the procedure be to continue from the point where it stopped?
1. click Reset?
2.
Then what?
Thanks
-
Unfortunately when you get an error or hit the e-stop button, you will lose position on the axes. If you have home switches installed, then you would rehome the machine to get back where you began.
Then, you can use "run from here" in Mach to start where you left off, but make sure you start from the line before as the run from here command can be a little tricky to get onto. Make sure you practice cutting in air above the workpiece to be sure it's going to do what you want it to do.
Dave
-
Every once in a long while I get a limit switch error while cutting. Or I press the e-stop button.
What would the procedure be to continue from the point where it stopped?
Restart program from the beginning. Anything else is going to foul up!
Cheers
-
Every once in a long while I get a limit switch error while cutting. Or I press the e-stop button.
What would the procedure be to continue from the point where it stopped?
Restart program from the beginning. Anything else is going to foul up!
Cheers
Dont agree, I always use RFH and have never had an issue. If you try to restart in the middle of a sub then yes you will have issues so start before but otherwise it should work.
One warning though if you are using the Demo version then it does not work as it is one of the few limitations.
Hood
-
Every once in a long while I get a limit switch error while cutting. Or I press the e-stop button.
What would the procedure be to continue from the point where it stopped?
Restart program from the beginning. Anything else is going to foul up!
Cheers
Absolutely not true! I often have need to interrupt, and re-start programs, and it's no big deal at all. First step is re-establishing correct offsets, which is usually just a matter of touching off on some feature of the part. Then, decide where in the program to pick up, click on "SetNextLine", then start running. You have to be careful about the start point you pick, to make sure any initial conditions are set correctly (modal settings, spindle/coolant state, etc.). Worst case, you may have to manually set a mode or two, or turn the spindle/coolant on, before re-starting. RunFromHere can also be used, but I have not had a need for that, and have seen it screw up with the dopey "preparatory moves", so I just don't use it.
Regards,
Ray L.
-
spindle/coolant on, before re-starting. RunFromHere can also be used, but I have not had a need for that, and have seen it screw up with the dopey "preparatory moves", so I just don't use it.
Regards,
Ray L.
I use RFH almost every day without too much fuss.
Thanks for the tip Ray - I'll try your method next time. the prep moves are sometimes a bit "scary" :-)
ATB
Derek
-
oops :-[
-
I thought that the RFH would be the thing to do, but it didn't work.
How does the RFH work?
I tried clicking on it but I had no movement, but it did scroll through the lines of code
??
-
Scroll to the line you want to start at then press RFH, it will scroll through the code and once done you press Start, a box will pop up with the prep move and option to start the spindle, if it looks like its OK then press OK and it will move to the position stated in prep move. Once there its just a case of pressing cycle start again. One thing worth mentioning is it works best if you have the safe Z enabled.
Hood
-
Scroll to the line you want to start at then press RFH, it will scroll through the code and once done you press Start, a box will pop up with the prep move and option to start the spindle, if it looks like its OK then press OK and it will move to the position stated in prep move. Once there its just a case of pressing cycle start again. One thing worth mentioning is it works best if you have the safe Z enabled.
Hood
I'll give that a try, Thanks!
You say it will scroll through the code. Will it go back to the line I selected?
What is involved in the "prep" move? What if it's already in the position I want to start from?
For example I press e-stop in the middle of a cut. So now it's stopped in between point X and Y.
Would I select point X as a restart point. Would the prep move be to go back to that point and wait for me to press "cycle start" again?
-
It will scroll from the start up to the point you have selected setting modal states etc.
If you press E-Stop whilst moving you have lost position so will need to rehome ( or retouch off the part and set the DROs if you dont home)
On the lathe I tend to start the RFH at the last tool change, on the mill I tend to start the RFH from the last point where the Z is above the work.
When you select the line to start your RFH it will actually start from the previous line so be aware of that, your prep move will show you that though if you look at its coords.
Hood
-
You say it will scroll through the code. Will it go back to the line I selected?
What is involved in the "prep" move? What if it's already in the position I want to start from?
For example I get an erroneous limit switch triggered in the middle of a cut. So now it's stopped in between point X and Y.
Would I select point X as a restart point. Would the prep move be to go back to that point and wait for me to press "cycle start" again?
So the e-stop and the limit switch are handled differently? I thought that they were the same. Live and learn!
In my instance where I get an erroneous limit switch triggered every once in a long while, would what I said in my last post (above) hold true in that instance?
-
No, Limit switch triggering whilst in motion is the same as the E-Stop in that you will almost certainly have lost position so you need to re-home before you can continue.
Hood
-
Hi Hood
I can see why RFH will work for some but not for others. If the program is a long file with all the data spread throughout, is is often used for surface routing, then OK, it will certainly work - as long as the e-stop has not lost position.
But my programming is extremely parametric, and that makes things a whole lot more complex for restarting. For a start, it seems to foul up any repeat subroutine loops because the counters and incremented variables are wrong.
The technique i use is to make my root program just a series of subroutine calls, with each subroutine doing one operation. Then I can go back to the root program and comment out all the completed stages, so that restarting jumps straight to the errant subroutine stage. Having first correct the programming error of course!
Cheers
-
Yes doesnt work in these situations but your statement Restart program from the beginning. Anything else is going to foul up! would suggest RFH would always "foul up" Where it actually works very well in most situations and I would imagine 90% plus of users dont programme parametrically.
Hood
-
Yes doesnt work in these situations but your statement Restart program from the beginning. Anything else is going to foul up! would suggest RFH would always "foul up" Where it actually works very well in most situations and I would imagine 90% plus of users dont programme parametrically.
Hey, I was only half-awake at the time!
But I was wrong.
Cheers
-
Ha ha, not wrong, for your situation it was correct but not for all, just wanted to clarify things as I use it all the time and have never, and I mean never had it go wrong in over 8 yrs. Most of my programming is wizard or CAM and no parametric at all.
Hood