Hi,
I've started using the Machining Extensions of Fusion and for rotary four axis tool paths the more normal Clearance Height optin in the Fusion post no longer works.
G30 is the other good option, but I've never used it before and was struggling to understand how it works. I am reasonably happy about how
it works now but still need to use it properly.
I have used the G30 option in the Fusion post, and
now I understand how G30 works its doing exactly as required and as coded. Thus I can have
no complaints about the Fusion post.
I understand I can put the machine coordinates of the safe location in the P1 variables, and that would be fine for say a tool changer which never varies
however I'm trying to replicate a Clearnce Height option For this I would require the Z axis to retract say 50mm above the external diameter of the part.
The X, Y location could be just its current X,Y location......ie
G91 G30 P1 Z10 would work. My understanding is that this would leave the X,Y location unchanged, the Z axis would retract upward by 10mm and then drive to the
Z coordinate of the P1 location. This would be fine.
This is the final few lines of code of a Gcode file produced by Fusion with rotary toolpaths:
M9
G30 G91 Z0.
G90
G0 A0.
G30 G91 X0. Y0.
G90
M30
Excepting that the Z axis does not retract to an intermediate point this combination works just fine....IF.....I program P1 location properly.
My plan is to write a small macro which would populate the P1 location in # variables, and that data could be derived from the existing G54.....or whatever
work coordinate set is in use. I cannot find a way for a macro to interrogate Machs core to provide the current work coordinate set. Can anyone think of a means to do so?
I'm thinking something like:
local CurrentSet= mc.mcGet?
(inst) --CurrentSet is an integer describing the current work coordinate offsets in use, eg '54' for G54, '55' for G55 etc
The remainder of the macro would extract the work offsets from the current set, and then apply at least the X and Y offsets directly to the P1 location and the Z offset
would be augmented by some reasonable value for clearance, say 50mm, and that applied to the Z coordinate of the P1 location.
If I can achieve this then I think I could put a macro call into the Gcode file produced by Fusion and it would automatically populate the P1 location and would
require no editing of the existing Fusion code.
Thats the theory......what is actually practical remains to be seen!
Craig