LinkBack URL
About LinkBacks
At least on 0i series controls, there is no such variable.
#4120 contains the last T-code commanded.
| | |
Hi Everyone,
First off, I want to say; "Wow!"This data base and forum are HUGE! I hardly know where to begin. Even the welcome page is intimidating!
Therefore, I decided to plug my nose and jump right in by asking you guys to help me with a problem I'm having.
At work, we're running Kitamura MyCenter Horizontals with 16 controls. I've been working on a tool lasering program that allows operators to laser tools on the fly without ever leaving auto mode or stopping the program. I have all the bugs worked out but I want to add a step which requires my ability to access the tool count value from the Tool Life Management. So far, everybody I've asked has been stumped.
Does anybody know the series of variables associated to the counter for each tool group?
Thanks in advance for any and all help!
Adam
At least on 0i series controls, there is no such variable.
#4120 contains the last T-code commanded.
Thanks, sinha_nsit, even though that's the news I don't wish to hear. Your not the first person to tell me that, or at least, the possibility of it.Originally Posted by sinha_nsit
How can that work?
There is a value stored somewhere and the capability of a 'Check Tool Life' alarm means that the control has access to the tool count value in order to throw the alarm. How can it do all this without an accessible variable?
Thanks
In the "Sample Program" section of "Custom Macro" chapter in Fanuc Operator's Manual, there is a program given which counts the usage time of different tools and stores them in permanent common variables (#500 series), using system variables #3002. I think this is close to what you want.
Sinha
I plugged it in MDI mode as #199=#3002 and it came up with a value of zero. I even tried it while a tool from the tool group was in the spindle and another tool group (with a count above zero, of course) was in the staging pot and it still came up with a value of zero.
I'm probably going to open a case with Fanuc. This bugger seems to be really buried.
I hate to keep burdening people with this problem and I am greatly appreciative of all and any help.
Thank you, Sinha!
I never did use tool life counts so I may be a bit off base but are they not used on the PMC side of the control? If that's the case it may all be handled on that side and there won't be much from a variable standpoint to track these thru a macro.
Please correct me if I am wrong.
Stevo
Use #500 series. #199 gets reset with M30.
I will. I was just doing that as a test.
Not always. I have all of mine set up to only clear at power down. I cut some parts of the manual below.
With a reset operation, local variables and common variables #100 to
#149 are cleared to null values. They can be prevented from being cleared
by setting, CLV and CCV (bits 7 and 6 of parameter 6001). System
variables #1000 to #1133 are not cleared.
A reset operation clears any called states of custom macro programs and
subprograms, and any DO states, and returns control to the main program.
Common variables can be shared among different
macro programs. When the power is
turned off, variables #100 to #149 are initialized
to null. Variables #500 to #531 hold data
even when the power is turned off. As an option,
common variables #150 to #199 and
#532 to #999 are also available. However,
when these values are using, the length of the
tape that can be used for storage decreases
by 8.5 m.
Stevo
Right.
I only talked about usual settings.
It is even possible to retain local variables after M30 (6001#7), but very few people might be using this.
Posting Permissions
| | |
