Several people have said that everyone-sooner or later crashes their router. What causes the crashes, human error or computer or what?
From contributor A:
All of the above and then some! As much as manufacturers try you can never truly eliminate human error from the equation. And not just at the interface (operatorís) level. Sometimes the programmer makes a mistake, sometimes the draftsman did not create a clean drawing which was posted and sent to the machine with errant code ( now you have two in house entities affecting the code). Sometimes the CAM manufacturer "tweeked" the post instead of "tweaked" it ( but usually they say theirs with a disclaimer that the machine control should have caught it) and letís not forget the machine control who's motherboard was beginning to show signs of failure and failed to recognize a legitimate tool offset. I know, I went to the extreme, but I think often we forget that all of the high production, and all of the convenience of CNC comes with a price - the price is simply learning the inherent complexity of the system you have and understanding as much as possible, if only to insure past mistakes are not repeated. Failure is succeeding in proving that the failed technique wonít work! Can I program, tool, and set up a CNC machine and not crash? Yes. Can I do it 99 out of 100 times? Probably. Can I guarantee it to never crash? No. To me, the key will always be to understand as much as possible about all of the systems within my manufacturing application, including the machine, the control, the tooling, the offline software, etc.
Posted by: Fred 12/31 [ #9 -- Re: CNC Router crash, why? ]
To contributor C: Yes I have, because I have used some on a tryout basis. The Stop On Collision feature was not one I found helpful. There were other goodies that interested me more. In the last 16 years I can not remember a machine crash caused by programming issues. I have caught a few by examining code, but they never ran at the machine. Almost all of the bad things happen by bad set up or operator error or inattentiveness. Anyway, I guess my point is, with 3 or 4 axis machines, those sorts of programming issues that can cause crashes are found during initial debugging of the post when the machine is new. Unless we are talking about 5 axis machines or specialized machines with elaborate fixturing, verification software is nice to have, but not necessary in most applications. Again, if you know the code and the machine the average guy can be trouble free. If you only want to draw product and apply toolpaths without going near the machine, then you probably will benefit from toolpath verification software. I didn't mean my original post to sound as if the software is a waste of money because it isn't in certain applications.