from our friends at Tormach
M1 functions as a “break” or “optional stop.” A couple of well-placed M1 commands in your program can allow you an extra check to make sure your tool offsets are where you think they are.
Your CAM won’t typically put these in, so you’ll have to add them to your program after the post. Consider the code snippet below:
N5 G90 G20
N10 M06 T2
N15 M03 S1200
N20 G00 X1 Y1
N21 G00 Z2
N30 G01 Z-0.25 F5
N45 X1 Y1 Z-0.125
N50 G00 Z1
N55 X0 Y0
(Absolute and inch programming)
(Tool change, Tool #2)
(Spindle on CW, at 1200 rpm)
(Rapid to X1,Y1)
(Rapid down to Z=2)
(Rapid down to Z0.1)
(Feed move down to a depth of .25”)
(Feed move to Y3)
(Feed to X5)
(Feed to X1,Y1,Z -0.125)
(Rapid up to Z1)
(Rapid over to X0,Y0)
(End of program)
Inserting lines N21, N22 and N26 into the existing code give you a chance for a sanity check on your tool offsets and may save you from an unanticipated crash. If you want, in addition to adding these lines near the beginning of the code, you can add them in a similar fashion after every tool change command.
Once you’ve got confidence in your program, most controllers can be set to ignore M1. Otherwise, you can always just go back through the program and delete each line that you added.
Please do us a tremendous favor and forward this e-mail to your machining friends
Please do us a tremendous favor and forward this e-mail on to your machining friends!
Are you not a subscriber to DIGITAL MACHINIST? Visit us at www.digitalmachinist.net and request a no-obligation issue, or call and request it at 1-800-447-7367. Tell them you received an e-mail from a friend!
Your friend thinks you’ll enjoy DM, or you wouldn’t have this e-mail!
We hope you enjoyed this e-mail tip, brought to you by your friends at Digital Machinist.
Do you enjoy our e-mail tips? Has one of them ever “knocked something loose” in your head? Your tip could be a future e-mail blast from your favorite magazine. Just send your tips to george.bulliss@VPDemandCreation.com. If we use your tip, we will extend your subscription by an issue. We like to see 200 to 300 words, plus an image, if available. Thanks!