Changing tool number in MasterCam 2018

[jjspur]

I have now had multiple instances where after I edit a tool number in MasterCam 2018 it will not recognize the new tool number and posts out the old tool number. The only remedy I have found thus far is pulling a new tool from the tool library and changing the tool number before creating the path. Has anyone else had this issue or am I the only one seeing this.

[Guest]

Try going into the the Tool Manager

Double click on the tool to open the maner and changing the tool # in there...

I have had it work before

[neurosis]

I've been doing it the way that JP showed above and haven't had any problems.   You can also try regenerating the operations after changing the tool number. I've had that work for me in the past.

[jeff]

On 9/8/2017 at 4:57 PM, Neurosis said:

  You can also try regenerating the operations after changing the tool number. I've had that work for me in the past.

That's what I do.

And if that still doesn't work, what I do is change it to a bogus number, regen, change it to the number you want and regen again. That always works. ::knock on wood::

[Goldorak]

right click on the tool and edit tool, change tool # from the manager , this way you will be sure that the tool number, tool length and tool diameter still the same # 

 

 

[SlaveCam]

9 hours ago, jeff said:

That's what I do.

And if that still doesn't work, what I do is change it to a bogus number, regen, change it to the number you want and regen again. That always works. ::knock on wood::

I never cease to wonder why there is no force regenerate button. Still in 2018.

[3R!< W3NG3R]

On 9/13/2017 at 5:48 PM, SlaveCam said:

I never cease to wonder why there is no force regenerate button. Still in 2018.

You think changing the tool number should cause a forced regen? 

[huskermcdoogle]

On 9/15/2017 at 7:18 AM, 3R!< W3NG3R said:

You think changing the tool number should cause a forced regen? 

Based on the fact that the NCI is being updated, yes.  I don't know, but I personally feel any change should force a regen on that standpoint.  But I will agree with all that it is ridiculous to have to regen ops for things that don't change the toolpath motion.  It gets tricky/annoying when you have to regen to make mics ints and reals take when the op doesn't go dirty....

[crazy^millman]

1 hour ago, huskermcdoogle said:

Based on the fact that the NCI is being updated, yes.  I don't know, but I personally feel any change should force a regen on that standpoint.  But I will agree with all that it is ridiculous to have to regen ops for things that don't change the toolpath motion.  It gets tricky/annoying when you have to regen to make mics ints and reals take when the op doesn't go dirty....

I have wasted hours needing to change mi for bias angle on limited Travel 5 Axis machines because the Software is not kinematic aware.

[jlw™]

same here.

[huskermcdoogle]

3 hours ago, C^Millman said:

I have wasted hours needing to change mi for bias angle on limited Travel 5 Axis machines because the Software is not kinematic aware.

Doing that right now.  

 

[jjspur]

Ok so this just happened to me again and I did both the method of changing it in the tool manager and regenerating tool path and it worked. I do believe that just regenerating will fix the problem at this point. 

[Matthew Hajicek - Singularity]

If Mastercam is failing to update something unless the op is regened, then obviously changing that should mark it dirty.  Changing the tool number SHOULDN'T require regen, but in reality it does.  I've had this bite me before, when after changing the tool number the code will post correctly, but the Vericut interface will pass the old tool number.

[volsfan911]

It's been doing that for me too and I just had the same problem when changing a Speed, it still posted out the old speed. I have never had this problem in other vers and it's a PITA!!! Glad is not just me I was beginning to think I messed up my post somehow.