• This site uses cookies. By continuing to use this site, you are agreeing to our use of cookies. Learn more.
[4]

G42 Then G41

[3]
[10] Like what you see?
Click here to donate to this forum and upgrade your account!

ranch23

Active User
Active Member
Joined
Mar 12, 2012
Messages
323
Likes
7
#1
If I make a G42 move can I then make a G41 move without cancelling and reinstating?
 

Tony Wells

Former Vice President
Staff member
Administrator
Joined
Jan 22, 2011
Messages
6,880
Likes
1,916
#2
Depends on the control. Can you plot the toolpath with your software and see how it handles it? If it doesn't like it you will have to stick a G40 between them.
 

ranch23

Active User
Active Member
Joined
Mar 12, 2012
Messages
323
Likes
7
#3
Really didn't have time, just cancelled it and then re instatedit, but I will try it the other way to see if it works or not. Thank You.
 

wrat

Active Member
Active Member
Joined
Oct 16, 2014
Messages
171
Likes
120
#4
On some controllers, like the old Fanucs, any time you change cutter comp, you have to put an intermediate point in there simply to "resolve" the comp.
When you're coming off of something, it's no big deal because, of course, the cutter isn't in contact.
But when you're going onto something, you need to turn it on; approach the part to a point not in contact, thus giving it a spot to introduce the comp; then start cutting.
Turning it on and off is no big deal, just gotta put in an extra point or two that you don't care about. On a controller that might not be smart enough, turning it on and off will result in a 'taper' as it moves to the comp position on the NEXT point. This can be a real frustration if you don't expect it (I know).
Equally inconvenient are some of the newer controllers that read the comp and move exactly then. This can result in gouging if it's in an inconvenient spot.
I don't recall a time i've switched from RH to LH (G42 to G41) comp, only to and from LH and cancel (G41 and G40).
Myself, i'd just input it as another block. No big deal. Just cancel (G40) each time. That way there's no chance of any lingering data stuck in some register somewhere that could create a mystery problem sometime down the road. But i'm generally extra careful like that, anyway.


Wrat
 
[6]
[5] [7]