ntraub01
04-16-2015, 06:04 PM
After months of design, prototyping and nail biting, yesterday was the day we started the milling process. I had been double checking and triple checking everything before we started and I was confident that all was going to go well.
This single piece of material, a 4'x8' piece of 1" cast plex, was the most expensive material I have ever milled so I was a bit nervous.
All was going well, but for some reason a bit broke while doing a profile cut. NBD So I slowed the feed rate on 1/4" bit down to 3"/sec and that went well.
Then I had 20-5/16" holes to pocket down through the material. The first two holes went ok but I was a bit concerned about the plunge rate. I interrupted the cut, insert command, VS, and changed the move and jog speed of the z axis, restarted the machine and within seconds the day went from great to bad.
In the two seconds after restart the machine plunged back into the hole it had just finished and didn't wait long enough for the bit to return to a safe height before moving and took about a 1" long gash out of the material, AND broke the bit!!
SOOO, it was a very expensive day yesterday with 2 bits being broken at $50 each and a ruined $600 piece of plex. Between the broken bits, the new bits I had to order and the ruined piece of plex, I'm at -$800 for the day!!
Needless to say I turned off the machine, closed the computer, turned off the light and went home...
After a few hour and a couple of adult beverages I came to the conclusion that changing the speed of the z axis, mid-cut using an Insert Command, VS, Restart process was probably NOT the smartest thing.
I'm guessing that the VS change really didn't make all of the changes necessary to the script to keep the error from happening?!?! Like it didn't change the pause timing for the bit to be pulled safely from the hole before moving again?!?
I'm also guessing that when we change speeds on say the XY move and jog that it doesn't really have to change anything else to keep an error from occurring?!?
Am I correct in thinking that changing the z axis speeds is not a good idea especially if the bit has a long distance to travel before it is at a safe z height before moving?!?
No I'm not going to trash the $600 piece of plex. I'm going to continue milling the piece and because it is part of a sandwich with another piece of 3/8" plex on top of the 1" piece, I'm going to pray that it isn't noticeable. However, if it is I may also attempt to route a larger circle and plug it with a plug and weld it into place hoping for a flawless or near flawless joint.
There you have it ladies and gentlemen, be VERY careful about changing z axis move and jog rates using the stop, Insert Command, VS method as you may not get what you expect!!
This single piece of material, a 4'x8' piece of 1" cast plex, was the most expensive material I have ever milled so I was a bit nervous.
All was going well, but for some reason a bit broke while doing a profile cut. NBD So I slowed the feed rate on 1/4" bit down to 3"/sec and that went well.
Then I had 20-5/16" holes to pocket down through the material. The first two holes went ok but I was a bit concerned about the plunge rate. I interrupted the cut, insert command, VS, and changed the move and jog speed of the z axis, restarted the machine and within seconds the day went from great to bad.
In the two seconds after restart the machine plunged back into the hole it had just finished and didn't wait long enough for the bit to return to a safe height before moving and took about a 1" long gash out of the material, AND broke the bit!!
SOOO, it was a very expensive day yesterday with 2 bits being broken at $50 each and a ruined $600 piece of plex. Between the broken bits, the new bits I had to order and the ruined piece of plex, I'm at -$800 for the day!!
Needless to say I turned off the machine, closed the computer, turned off the light and went home...
After a few hour and a couple of adult beverages I came to the conclusion that changing the speed of the z axis, mid-cut using an Insert Command, VS, Restart process was probably NOT the smartest thing.
I'm guessing that the VS change really didn't make all of the changes necessary to the script to keep the error from happening?!?! Like it didn't change the pause timing for the bit to be pulled safely from the hole before moving again?!?
I'm also guessing that when we change speeds on say the XY move and jog that it doesn't really have to change anything else to keep an error from occurring?!?
Am I correct in thinking that changing the z axis speeds is not a good idea especially if the bit has a long distance to travel before it is at a safe z height before moving?!?
No I'm not going to trash the $600 piece of plex. I'm going to continue milling the piece and because it is part of a sandwich with another piece of 3/8" plex on top of the 1" piece, I'm going to pray that it isn't noticeable. However, if it is I may also attempt to route a larger circle and plug it with a plug and weld it into place hoping for a flawless or near flawless joint.
There you have it ladies and gentlemen, be VERY careful about changing z axis move and jog rates using the stop, Insert Command, VS method as you may not get what you expect!!