.. . Every tool number from 15 to 25 are empty..
What do you mean by "empty" ?
Make it 'not empty'
Can you see all 25 tool frames in the Frames menu?
And how do you try to "work with any of them"?
Can you see all 25 tool frames in the Frames menu?
And how do you try to "work with any of them"?
Yes i can see all of them
In the Jog coodinate System when i select for example Tool 15, i directly receive the error SSPC-115 Invalid Tool number (ST,G:1)
An auto update may fix this, but I'm not very confident in it.
There are a lot of settings/utilities that don't play nice outside of the default range of tool/frame numbers.
In the Jog coordinate System when i select for example Tool 15...
Not clear what procedure you mean by this.
Are you able to set it as active tool in the Frame setup menu?
Not clear what procedure you mean by this.
Are you able to set it as active tool in the Frame setup menu?
Yes that's what i wanted to say but as soon as i set it as active tool i get the alarm
Not clear what procedure you mean by this.
Are you able to set it as active tool in the Frame setup menu?
I have a similar problem and i tried several ways to set it as active tool.
- SHIFT + COORD
- Selecting the tool on the navigator panel on Roboguide
- In the Menu -> Setup -> Frame SETIND
- Even by changing the value of the system variable $MNTOOLNUM[]
- By running a program to change the UTOOL_NUM
However, all theses method endup giving me the same error as the one posted on this thread
Well, in case of deficiency of tool frames, I would store them in position registers and emulate selecting tool frame by executing UFRAME[..]=PR[..]
Well, in case of deficiency of tool frames, I would store them in position registers and emulate selecting tool frame by executing UFRAME[..]=PR[..]
Same problem, as soon as i run it the same error appears
It looks like you misunderstood the idea.
You should always use a valid tool number, e.g.Utool 1.
Instead of changing UTOOL number, you reassign the tool frame values, from certain PR.
There are multiple software bugs on Fanuc when going beyond UT 10. If you really need more then Sergei Troizky solution is a good work around.
Pick a UT that won't be fixed, but instead you will change programmatically. For example UT[9].
Then for any extra UT you need, store them in PRs instead. Then whenever needed you can write them back into UT[9].
