How do I get an Op.1 setup & Op.2 setup into a single program with 2 work offsets?

[chrisevrard]

Hey All,

I spent way too much time looking at YT vids on this one, but didn't find an answer. 

I have a program that starts 5 parts in the first setup (single piece of stock) and finishes the 5 parts in the second set up in a set of soft jaws.

I want to set up one vise for op. 1 and another vise with the soft jaws for op. 2. (a G54 vise and a G55 vise) 

Is there a way to get Op. 1 setup & Op. 2 set up to post into a single program where Op. 1 is G54 and Op. 2 is G55?

Thank you!

Chris E. 

[Marco.Takx · Accepted solution]

Hi @chrisevrard,

A couple this you did wrong and forgot.

1. Within the setups you have to define with WCS on the machine you like to use (Setup 1 set it to 1 (G54) and setup set it to 2 (G55))
   
2. Then you can post both setups at once into a single nc program.
   And use the Reorder and minimal tool change. To make a optimal nc program without a lot of tool changes.
   
   But you first have to fix the tools into your programming.
   I see double tools that are the same.
   That means that the option Reorder and minimal tool change can't work because for him these are different tools.
   Also you have same tool numbers on different tools.
   
   Hopefully this makes sense for you.
   
   If my post answers your question Please use Accept as Solution & Kudos This helps everyone find answers more quickly!
    

[chrisevrard]

Yes, it seems to make sense. I'm going to fool with it this afternoon. Fingers crossed!

I know I need to clean up the tools first too. I was copying and pasting in tool paths from another program. It is a mess! Lol. 

Thank you very much,

CE 

[chrisevrard]

So I tried the above and it seemed to work. I did get a program with G 54's and 55's. Yay!

But I also got the following message. Is this just warning me to have a clear path between work offsets, or do I really have to go and customize/edit my post processor in some way?

Thx!  

[seth.madore]

No editing required. It's just another case of us protecting the user from themselves. It gets annoying (personally speaking) as I'm always posting out programs for my Doosan Lynx that has main and sub spindles. Same warning is generated in that case.