Cancel
Showing results for 
Search instead for 
Did you mean: 

[ISV]Set Tool Change

Solution Partner Builder Solution Partner Builder
Solution Partner Builder

Hi

 

setup is millturn. The problem is tool change.

 

Code bloak is "T001 T002 M06" (Tool change for No.1, and set No.2 as next tool)

 

It is currently being exchanged for the Next tool (TOO2).

 

I am going to exchange it with the current tool.
How do I set it up?

4 REPLIES

Re: [ISV]Set Tool Change

Siemens Phenom Siemens Phenom
Siemens Phenom

Hello,

 

This could be achieved by using instances. See the CSE documentaion at:

Common Kernel Commands -> Basics ->
Metacode Handling

The idea is, that together with the M6 you catch all T metacode with MCParam and then check how mayn are programmed, and which one you will use for what. Below a snapshot as an EXAMPLE:

(The local variable is not used. Only for the use you might need both T values. In that implementation the 2nd tool number is ignored – this assumes the ‘normal’ NC code always looks like T T M.)

 

using_instances.jpg

Thomas Schulz
Siemens PLM
Manufacturing Engineering Software

Re: [ISV]Set Tool Change

Siemens Legend Siemens Legend
Siemens Legend

If you don't have an MTK license to edit the CSE driver, or do not want to try and edit the CSE driver, you can accomplish this with the post processor. There is a mom variable, mom_post_in_simulation, that checks to see if output is to be posted for machine, or if you are in simulation. In the post you define two tool change blocks, one the Txxx Txxx M06, the other with Txxx M6. Useing a check block to test wich condition the post is in and set the output. So if in simulation post will output Txxx M06, and when posting for the machine post will output Txxx Txxx M06.

I have attached a sample post that has all this in it.

 

Step 1)

Create a PB-CMD check block for machine output. Notice the __ double underscore, this lets post builder know that it is a chcek block.

 

if{ [ info exists mom_post_in_simulation ] && $mom_post_in_simulation == 0  } {

return 1

} else {

return 0

}

ScreenHunter_01 Apr. 03 08.38.gif

 

Step 2) Create a PB-CMD check block for machine simulation.

 

if{ [ info exists mom_post_in_simulation ] && $mom_post_in_simulation == "CSE"  } {

return 1

} else {

return 0

}

ScreenHunter_02 Apr. 03 08.38.gif

 

Step 3) Create both blocks in post builder.

ScreenHunter_03 Apr. 03 08.39.gif

 

Step 4) Add check block test to post output block, double click block to open for edit. Right mouse button pick on top left hand corner of block in darker boarder, move mouse over Output Condition, select check block for post to machine.ScreenHunter_04 Apr. 03 08.39.gif

 

Step 5) Repete step 4 for simuluation block

ScreenHunter_05 Apr. 03 08.40.gif

 

Output for Simulation:

ScreenHunter_06 Apr. 03 08.40.gif

Output for machine:

ScreenHunter_07 Apr. 03 08.40.gif

Re: [ISV]Set Tool Change

Siemens Phenom Siemens Phenom
Siemens Phenom

Thanks to Mike for that alternative workaround. Please be aware using these command as rarely as possible, because you simulate not exactly the NC code which will be send to the machine.

 

For sure if you know what you are doing this is a possible solution to your topic

Thomas

 

Thomas Schulz
Siemens PLM
Manufacturing Engineering Software

Re: [ISV]Set Tool Change

Siemens Legend Siemens Legend
Siemens Legend

I would not suggest to do this on a block that would result in a change in motion on the machine...

Learn online





Solution Information