Moving cut stock with work offset change

DENNISG · 2005-06-15 17:47:47

We have dedicated tooling and standard work offset positions on a machine. The part position in each sattion varies accordingly to geometry I would like to add a move cut stock from position1 to Position2 macro to be triggered by the work offset. I.E. G55 triggers move cut stock from postion1 to position2, G56 triggers move cut stock from position2 to position three etc... Can I put seperate words g55, g56, g57 in the control and have a macro run under each word? What should the macro statment look like? I need a little direction. Thanks

SergeV · 2005-06-17 18:20:44

Create a Coordinate System for each position. Make sure the CSYS are associated to the Stock Component. Name your CSYS: G54, G55, G56, ...

In the Control, with G55, add the following macros:
MoveCutStockFromCsys with an override text= G54
MoveCutStockToCsys with an override text= G55

Same for G56, etc...

To test the move manually, stop at G55, Model > Model Definition; Position tab; Csys tab:
From = G54, To = G55, Move

DENNISG · 2005-06-17 19:03:36

Thanks Serege, this works great but there is one more issue. I would like this to occur only on the first occurance of G55. Can I assign a variable to increment everytime g55 occurs and the use an if/then statment to execute the macro as long as the variable is not < 1.

SergeV · 2005-06-17 20:08:32

set the G55 with the translation with a condition "Not equal" to zero,(there are no "greater than" for conditions). And after the moveStock... macros, set the variable to a value of 1.
Add a condition where the variable equals 1, then only call the work offset macro.

Use a diffeent variable for G56, 57 ect...

I would recommend creating a text variable instead of the # number. This way there is no chances of conflict with variabless you would use in your programs.

Setup> Control> Word Format > Add
Name = variable_g55
Type = Special
Sub-Type = Variable Name

DENNISG · 2005-06-17 22:48:19

Excellent I got it working. But I am having troble with the "Add a condition where the variable equals 1, then only call the work offset macro. " I assume I need another conditional statement dircecty under the G55
Currently I have
G55
not (Variable: VARIABLE_G55 1)
Variable: 4014
WorkCoord
MoveCutStockFromCsys
MoveCutStockToCsys
Variable: VARIABLE_G55
[Iwould think here Should be]
(Variable: VARIABLE_G55 1)[ or something like it.]
Variable: 4014
WorkCoord
When I add a condition I get a statment

not (Variable: VARIABLE_G55 1) and (Variable: VARIABLE_G55 0)
Which dosen't make sense to me logically.

Thanks for all your help

SergeV · 2005-06-17 23:23:23

here is an image of my configuration

ftp://ftp.cgtech.com/pub/csys_example.jpg

Note: I just did it for G55 and G56

the 2 conditions are, variable_G55 is equal to zero or it's not.

DENNISG · 2005-06-18 12:45:42

DONE THANKS FOR YOUR HELP AGAIN

DENNISG · 2005-08-30 17:17:41

Serge
Can I make this work for extented work offsets I.E. G54.1P01...P02...P03
I experimented putting this in the P register. I was also trying to use the gcode tables work offset to channge coordinate system. For g54 the register is 54 but for g54.1 p01 what should the register be? 1 does not work.

SergeV · 2005-08-30 20:23:15

For G54.1 P1, the register for the table should be 1. Make sure you created a Work Offset table. Compare your configuration for G54.1 and the word P with the settings in fanuc15m.ctl in the Library.

DENNISG · 2005-08-31 14:25:24

I want to control what happens when a specific P is called... G54.1P1 move cut stock pos1 to pos2 then G54.1P2 move cut stock pos2 to pos3 etc. I have a question about where to place things in the tree. I tried Placing it under P* it works but if I change the range it affects all codes. Then I added a new word P1 but his didn't seem to work either.

SergeV · 2005-08-31 15:34:28

Hi Dennis,

I would not recommend creating a word P1. simply change the range value like the M-codes or G-Codes.

If you change the Range to 1, you need to select Add instead of Modify. Then you have a new condition, you need to copy all the macros from P * into P 1 and P 2, etc...

This will avoid any conflicts when P is used with other codes like G4, G5, ...

Make sure that the new ranges you add are located before the P *.

DENNISG · 2005-08-31 16:20:10

Thanks Serge once again!!

VERICUT Users' Forum

#1 2005-06-15 17:47:47

Moving cut stock with work offset change

#2 2005-06-17 18:20:44

Re: Moving cut stock with work offset change

#3 2005-06-17 19:03:36

Re: Moving cut stock with work offset change

#4 2005-06-17 20:08:32

Re: Moving cut stock with work offset change

#5 2005-06-17 22:48:19

Re: Moving cut stock with work offset change

#6 2005-06-17 23:23:23

Re: Moving cut stock with work offset change

#7 2005-06-18 12:45:42

Re: Moving cut stock with work offset change

#8 2005-08-30 17:17:41

Re: Moving cut stock with work offset change

#9 2005-08-30 20:23:15

Re: Moving cut stock with work offset change

#10 2005-08-31 14:25:24

Re: Moving cut stock with work offset change

#11 2005-08-31 15:34:28

Re: Moving cut stock with work offset change

#12 2005-08-31 16:20:10

Re: Moving cut stock with work offset change

Board footer