"h" tool length offsets

[Guest]

I just double checked some of my programs and I am definitely calling G68 while G43 is active. Sounds like it's something you should be able to change with a parameter.

G68 or G68.2?

[jlw™]

My bad, I knew 68.2 won't do it so I just threw plain old 68 in with it.

 

Apologies.

[jlw™]

Either way, it hurts nothing to cancel it.  Preference.

[Sticky]

I'm just using G68.

[Guest]

There are different rules for use and cancellation of G68.2 than G68.

 

HTH

[civiceg]

 

I can't say I've ever seen that. By 'cancel" do you mean calling G49 and switching to G91? I can't see how you would actually clear the work offset register without making a macro to do it, which would be insane.

 

 

Had it happen on a FANUC 31i with regard to work offset. Program had been using an extended w/o. Had G28G91Z0 in between same tool operations for a re-clamp. It would default back to G54 and the change could be seen in the active command window. Crashes occurred and the post later fixed. 

[Sticky]

So Zero Return activated G54?

 

That would require some interesting ladder modifications. So this machine must have also defaulted to G54 every tool change as well. You might not have noticed if your post always called the correct offset at each tool change.

[Guest]

I always use G53 because I KNOW where it's going to go and what condition the machine will be in when it gets there. G53 doesn't cancel anything. It just goes to a position in Machine Coordinates.

 

JM2CFWIW YMMV

[Sticky]

I always use G53 because I KNOW where it's going to go and what condition the machine will be in when it gets there. G53 doesn't cancel anything. It just goes to a position in Machine Coordinates.

 

JM2CFWIW YMMV

 

Not unless the same d1pxxxx that setup civicegg's controller setup the control you are working on

 

It's always a bit "interesting" to see how some controls get setup.

[Guest]

Not unless the same d1pxxxx that setup civicegg's controller setup the control you are working on

 

It's always a bit "interesting" to see how some controls get setup.

He said G28 was wonky...

 

Civicegg... what machine was that that fid the weird G68 thing?

[Newbeeee™]

Not unless the same d1pxxxx that setup civicegg's controller setup the control you are working on

 

It's always a bit "interesting" to see how some controls get setup.

What makes me real annoyed is when you get sequential build numbers and the ladders are different, let alone parameters.

Sh!t like that is ridiculous - but I bet each engineer at the factory has their own 'special disc' to load from...

[Guest]

What makes me real annoyed is when you get sequential build numbers ...

 

Each builder is different when it comes to "sequential build".  Some builders serialize the casting order and not the production order so while the two s/n's may be sequential, their respective builds could be weeks or even months apart.

 

JM2CFWIW YMMV

[Newbeeee™]

Each builder is different when it comes to "sequential build".  Some builders serialize the casting order and not the production order so while the two s/n's may be sequential, their respective builds could be weeks or even months apart.

 

JM2CFWIW YMMV

No need to defend Matsuura - never had a problem with them...

[Sticky]

He said G28 was wonky...

 

Civicegg... what machine was that that fid the weird G68 thing?

 

I understand that, but someone either pooched the ladder in his control, or made a custom G code out of G28, both are completely insane. My point was, if someone is stupid enough to make a custom G code out of G28, they are stupid enough to make a custom G code out of G53.