What’s your advice on multi-work offsets?

[marker4x4]

Hi all, I hope you've had a good Summer

Anyway, I wonder what technique you guys use to create code with mutiple work offsets (G54, G55, and so on).
Basically, if you are going to mill several the same pieces and they're clamped in the vises, not on the fixture, you want to use individual work offsets and let the code do the positioning.

We almost always use fixtures for multi-piece machining, and that's easy to code with Subroutines. i'm not too sure how to output different G5's....

Anyhow, any advice - as usual - will be appreciated! Thanks,

 

[appinmi]

Within every NC sequence, there is a parameter "FIXT_OFFSET_REG" that is used to output the "G54, G55, etc.". If you are using G-post, you will need to create a FIL macro for the "SET/OFSETL" command that Proe will output. With the proper macro, you can even force the post to output the registers whether they have changed or not. There is nothing worse than going from "G54 X0 Y0" to "G55 X1.0 Y0" and not having the "Y0" output on the line because Y didn't change.

 

[marker4x4]

Within every NC sequence, there is a parameter "FIXT_OFFSET_REG" that is used to output the "G54, G55, etc.". If you are using G-post, you will need to create a FIL macro for the "SET/OFSETL" command that Proe will output. With the proper macro, you can even force the post to output the registers whether they have changed or not. There is nothing worse than going from "G54 X0 Y0" to "G55 X1.0 Y0" and not having the "Y0" output on the line because Y didn't change.

Yes, but I need to output the same sequence several times over with different G-offsets in order to gang-machine the parts. What I've done - and actually works fairly well so far is to create subroutines with Fixture-->Use Fixture Compensation box checked. All translate values are set for 0, I enter # of repetitions in the Number field, Initial register 54 and Increment 1.

My only grief is so far that Gpost issues the following warning:
SELECT G CODE OUTSIDE LIMITS - DEFAULT ASSUMED
... don't know why, my default Work Offset is G54.

Cheers,

 

[appinmi]

If your number of repititions is greater than six, you are exceeding the limits of the offset register, (G54, G55, G56, G57, G58, and G59). If you are less than or equal to six, then check your post. Open the post, then select "Machine Codes" and "Fixture Offsets". Check your minimum and maximum fields. They should be at 54 and 59. Also under the "Address" field, leave the minimum, maximum, and default values at "0.000000".

 

[marker4x4]

If your number of repititions is greater than six, you are exceeding the limits of the offset register, (G54, G55, G56, G57, G58, and G59). If you are less than or equal to six, then check your post. Open the post, then select "Machine Codes" and "Fixture Offsets". Check your minimum and maximum fields. They should be at 54 and 59. Also under the "Address" field, leave the minimum, maximum, and default values at "0.000000".

That's what it's set at; must be something else I suppose... I'll have to look closely when I have more time to play with that.
Thanks!

 

[marker4x4]

OK, this is the section that causes the WARNING in my .acl file:

RAPID
GOTO / -3.9900000000, -0.2800000000, 1.0000000000
SET / OFSETL, OFF
REMARK -> END /
REMARK -> FEATNO / 90
SET / OFSETL, 56

... and here's the WARNING in the .lst file:

54>RAPID
55 55 G000 Z1.0000$
56>OFSTNO/0
56 56 ***WARNING***
+&nbsp ;&nbsp ; SELECT G CODE OUTSIDE LIMITS - DEFAULT ASSUMED
56 56 G054$
59>OFSTNO/56
59 59 G000$
59 59 G056$

... and here's the code:

G0 Z1.
G54
G0
G56
G0 X2.9735

Is that the SET / OFSETL, OFF that causes the WARNING?
Just wondering, cheers

 

[appinmi]

What is happening, is that the value of the word "OFF" is outside the 54-59 limits. What you will need to do, is create a FIL macro to filter out and process only numeric, (real),values. Try using this macro:


View attachment 2665


I hope this helps;

 

[marker4x4]

What is happening, is that the value of the word "OFF" is outside the 54-59 limits. What you will need to do, is create a FIL macro to filter out and process only numeric, (real),values.

Yeah, that's what I thought...


I haven't tried the macro yet (no time, no time!!!!) But I'm sure it'll work well - as any other creations of youse

Thanks Allan, have a nice weekend