Renumber Tools

[MKTech]

I have made a new tool library with different tool numbers. But since we have many 1000 old programs, they all need to be renumbered. I wanted to write a script that queries me all the tools what new number they have. 

Since many operations have the cutting data adjusted separately I don't call "op.AssignMillToolBySlot(slot);" but set the number on the tool and still separately on the operation. The whole thing works, except for facing and slot milling. If I call there "op.Commit(false);" the geometry is discarded, also with true the same. Why?

Or how does it work differently? Can I also change the tool number without recalculating the operation? That would be much better.

Thanks for all ideas
Use Mastercam 2023

The actual code is attached

Renumberator.csx

[byte]

On 7/11/2023 at 2:17 PM, MKTech said:

I have made a new tool library with different tool numbers. But since we have many 1000 old programs, they all need to be renumbered. I wanted to write a script that queries me all the tools what new number they have. 

Since many operations have the cutting data adjusted separately I don't call "op.AssignMillToolBySlot(slot);" but set the number on the tool and still separately on the operation. The whole thing works, except for facing and slot milling. If I call there "op.Commit(false);" the geometry is discarded, also with true the same. Why?

Or how does it work differently? Can I also change the tool number without recalculating the operation? That would be much better.

Thanks for all ideas
Use Mastercam 2023

The actual code is attached

Renumberator.csx 1.51 kB · 10 downloads

Those operations are not supported by the api, there is also a bug with commit, the chook api is far better suited for these tasks,

for most tasks involving toolpaths the nethook api is not suitable