Z retract when switching work offsets in program
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report
I am hoping someone who has some skills in editing post processors can help me out with an "issue" I am having. I have tried to edit myself but am not having any luck.... when I post a program to use multiple WCS, the program will do a full Z retract from G54 TO G55 for example (on my okuma G15 H01 TO G15 H02). this is totally unnecessary for me, and just wastes time and motion especially when we are doing a large production job. We standardize everything to where we use the same vises, parallels, and operation in multiple stations so even clearing an inch or so would never cause a crash... I am actually more likely to cause a crash because of the fact that I have been hand editing every program to do my own desired retract when switching offsets and one of these days I am going to goof up and the machinist on the floor may miss my mistake... I am attaching an .F3D file along with the post processor I am using and a sample "target program" for reference. In my target program I just put a Z5.0 clearance when switching WCS which should be safe and efficient enough... In my .F3D file, I am using the "OP20" setup in the manufacturing workspace. I have multiple other posts that I need to do this to, and I am hoping if someone can fix this post I can kind of figure it out for my other ones...
It would be awesome if fusion gave us the option to set our own Z retract height when switching WCS and also when working on a 4 axis indexing job.... (Z also does a full retract when indexing an axis which 99% of the time in my case is totally unnecessary) I can see that maybe Autodesk is concerned of causing crashes, but the way I see it this is just another parameter that the programmer is responsible for to create a safe program just like everything else we have to decide when creating one....
Any help anyone can offer would be GREATLY APPRECIATED as this is something I have been trying to address for almost 2 years (it's been on the backburner, however)
Thanks,
Jeff