Tool Life Management is setup..some question

[ldouble619]

Hello all,

I have set up tool life on one of our machine, however I do have some questions and concerns..

1. How do I change my program to setup it up in cycles not minutes?


2. Is there anyway to alert the operator when the tool changes? Right now they are loading from the back of the machine, so they have no idea when a tool is being changed out and to inspect that part.

It would be nice to have them hit cycle start or something to confirm a new tool.

Thank you for the time.

[stevo1]

Welcome to the group.

You are forgetting 1 thing…..you never told us what kind of machine and control you are using.

There are many different ways that you can do this. I would personally set up a macro for counting the pieces and notify the operator of the tool change.

Stevo

[ldouble619]

Thank you.

The machine is a Mitsui seiki HW55. Controler is 31i


Thanks for the help.

[stevo1]

1. Do you have a programming or operator manual for this control?? There should be a timer for cycles as well as minutes. The manual should explain it.

2. You can put a message in the tool change macro. If you do not have one on this machine we can set one up either using the M6 code or the T code. It is very simple to do. You can have the machine stop and display a message along with needing the cycle start button pushed in order to continue.

Stevo

[MysticMonkey]

Maybe this will help

[ldouble619]

Originally Posted by stevo1 1. Do you have a programming or operator manual for this control?? There should be a timer for cycles as well as minutes. The manual should explain it. 2. You can put a message in the tool change macro. If you do not have one on this machine we can set one up either using the M6 code or the T code. It is very simple to do. You can have the machine stop and display a message along with needing the cycle start button pushed in order to continue. Stevo

I got number one taken care of, it was a param change 8430 I think..

Stevo, If you can help me with that, it would be awesome! What you describe is exactly what I need. However I have no idea how to do that.

Thanks for all the help.

[stevo1]

I have never worked on the 31i control so you should double check the syntax for this control.

First thing you have to do is see what programs are being called for your tool change macro if you have one set up. The best way to do this is by calling a tool and seeing if it jumps to a subprogram in the 9000 range. The other way to tell is looking at the parameters that need to be set in order to call a macro with an M-code. For your control the following parameters will call subprograms.
Parameters 6071-6079 calls programs 9001-9009
Parameters 6080-6089 calls programs 9020-9029

Check these parameters to see what they are set to. For example if parameter 6072 is set to 6 then program 9002 is going to be called when a M6 is programmed.

Once we establish which program is being called or if none are called then we will set one up to be called with every M6. For example sake lets set up program 9001 to be called with a M6. So set parameter 9001 to 6. Now make a 9001 program and you can write a stop inside of this program so that the operator has to push cycle start if a tool is changed.

Now IIRC #3006 is still the system variable to stop the control with a message in your control. You can set up the stop in a few different ways. You can use a M1 for optional stop, M0 for program stop, or #3006. If you ALWAYS want the program to stop then use M0 or #3006.

If you use M0 then the program will stop at that code and sit until cycle start is pushed. If you use #3006 then you have to program it like so.
#3006=1(tool change cycle start)
Now the program will stop and it will go to the message screen and display what you what written in the parenthesis on the screen. You can then push cycle start to continue.

If you have a program currently being called for the tool change then post that code so we can find the best place to insert the program stop.

Stevo

[sinha_nsit]

Originally Posted by stevo1 #3006=1(tool change cycle start) Now the program will stop and it will go to the message screen and display what you what written in the parenthesis on the screen. Stevo

As far as I remember, on my machine with 0i Mate TC, the message screen does not automatically come. The program does stop (and re-starts with CYCLE START button), but the message is displayed only after pressing the MESSAGE key. How can the message be automatically displayed?

[stevo1]

I have not worked enough on the Oi series control to notice the message is displayed after cycle start. So does that mean you have to push cycle start twice to continue the cycle? You say it stops with no message, then you push cycle start and it displays the message…..does it stop at that point as well or will it continue the cycle with the message displayed on the screen??

What does the screen display when it reads the #3006?? Does it stay in the main program and sit on the #3006 line like an M0??

On the 10,11,12,15,16,18,21 series and IIRC the O series when #3006 is set to 1 the screen will change to the message screen, display the message in parentheses and stop the cycle.

Stevo

[sinha_nsit]

CYCLE START is required to be pressed only once for restarting execution. Everything is same as in other control versions, except that the screen does not automatically change to message screen. If you want to see the message, you have to select message screen. If you wish, you can even restart execution without reading message. It is like M0. Possibly, it is parameter-related issue. If I come to know about it, I would post it here.

[stevo1]

Originally Posted by sinha_nsit CYCLE START is required to be pressed only once for restarting execution. Everything is same as in other control versions, except that the screen does not automatically change to message screen. If you want to see the message, you have to select message screen. If you wish, you can even restart execution without reading message. It is like M0. Possibly, it is parameter-related issue. If I come to know about it, I would post it here.

Huh….that is pretty weird. I have never seen that before. What is the point in having a program stop with a message if you are not going to display it? I would not even bother then with the #3006 and would just use M0 then. I would have to ass u me that it is a parameter setting. So does the code just stop on the #3006 line and sit?

Stevo

[sinha_nsit]

Yes, it works like M00. Just sits over #3006 line, waiting for CYCLE START to be pressed again.
This may be a parameter issue. I have just seen the following in 0i parameter manual (though I have not tested it):
3111#7 (NPA): Action taken when an alarm is generated or when an operator message is entered
0 : The display shifts to the alarm or message screen.
1 : The display does not shift to the alarm or message screen.