Strange problem with Mori AW22 / Fanuc 0T

[emexcee380]

Hey Mori Guys,

We have mid-80's Mori AW22 w/ Fanuc 0T control. This morning the program that has run for days began hanging up following a "T0600" command. (No alarm). When I checked Dgn 700, I saw that .1 was ON, meaning "A move command is being executed in automatic." No move command (G00 or G01 had been commanded but the PROGRAM CHECK screen showed a DIST TO GO of .002 for the z-axis. Hmmmm.......... I looked in the WEAR offset pages and saw a value of -.002 for tool 10 / z-axis. (Tool 6 WEAR had no value.) So I took the -.002 out of the WEAR offset for tool 10 and ran the program. No hang-up. Hmmmm.......

Then I put the value back in WEAR offset 10 and added a "G00" command in the line with the T0600. Again, no hang-up. ("WTF", I thought....)

So for some random, strange reason when the control is reading "T0600" it's picking up the WEAR offset value for Tool 10 and thinks it needs to move that amount to be finished.

This problem appeared after running the program without issue for several days.

Can anyone ("Underthetire" or other Mori specialist?) help me understand how/why this is happening?

Perplexed,

emexcee380

[EECENOD]

keeping in mind that g codes are modal , you should verify settings of parameter 14 to determine if offsets are activated by axis motion or the T code word...specifically bit 4....

[underthetire]

Never seen a AW22? Check the position/program check page and see if offset 10 is active before or after the T0600 call. I'm not super familiar with the 0 offset call outs, and I also know it depends on tool offset A,B,C option. There was some few machines that used a 6 digit T code, so it was tool position, offset, and wear or radius, but I can't remember if those were set up to act like an Okuma, or came from the factory that way.

[emexcee380]

Hey guys,

(Sorry, Mr. Tire.... The machine model is an "AL-22S" , not an AW. I'm so old and my brain so bogged down with drivel it's a wonder I can even spell, much less correctly.)

Thanks for the responses. Keep in mind however that we've been running the same program for days and then this problem started. And now that I think about it, we had a similar problem on our Mori ZL-15 w/ Fanuc 0TT right across the aisle a few months ago.)

What in the world would cause the control to process a WEAR offset value for another tool and apply it to the tool that is currently commanded?

By the way, the program code looks like:

N16;
G28U0W0M5;
G30H0;
T0600;
G50S2000;
G96S350M204;

and so on.....

At the "T0600;" command, the DIST. TO GO (Z) suddenly displays ".002" even though the WEAR offset for T6 has no value in it. The WEAR offset for T10 has a value of "-.002" (Z) in it and this is where the control is getting the value. Now, since the control thinks it's got to move another .002" to finish the block, it sits there until we RESET.

We can cause the program to run by deleting the WEAR offset value for T10 or by inserting a "G00" command in front of the "T0600" command.

Any thoughts?

Thanks,

emexcee380