I had an issue recently using an mpg to drill a hole when doing this i had what could only be described as an un-commanded toolchange mid drill which led to an estop and brown trousers, anyone heard of this ?

I have been trying to run some code but do not understand an un-commanded move after the tool change, below is the code.

Between the tool change and the M03 line the X axis runs towards the centreline the Z stays still, does that seem to be right ?

Then both axis move to the commanded positions on line N180

Now if i stop the program, rewind and run again the X axis will move to a different position ?

All the above was stepping through one line at a time.

OK now i let the program run completely at the end the axis move to the commanded positions BUT THEN THE TOOL CO ORDINATES CHANGE TO TOOL ONE BUT TOOL 05 IS STILL IN THE TOOL DRO. Is that correct behaviour ?

I have tried using my desktop as i am running this on a laptop with SS with the same results

I have the same issue with ver 3.042.029 as with 3.042.023 i have tried changing persistent tools unticked restarting Mach same problem.

Yet another issue is homing, i am using optical sensors and it works perfectly but occasionally it appears that the motors have retuned themselves as it doesn't back of the same distance restarting Mach will cure the problem.

I have completely lost confidence in the machine.

I have attached my XML if someone could help

%
O0000
N90 G96 G94 G90 G80 G64 G54 G50 G49 G40 G21 G18 G00
N130 M06
N140 T0505
N150 G97 S500
N160 G95 F1.5
N170 M03
N180 G00 Z50. X60.
N190 Z1.
N200 X12.
N210 X9.8
N220 G32 Z-20. F1.5
N230 G00 X12.
N720 Z1.
N730 X60.
N740 Z50.
N750 G50
N760 M5
N770 M9
N780 (END TOOL)
N790 M30
%

Nobody able to offer any insight. 

Maybe a change in title will get me some help

PHIL,
I have used the MPG to do move the axis to cut off, drill holes, and turn down small stuff and didn't
have any problems. Can't help because i don't use the tool changing or have limit swithes yet on the lathe.
I am sure someone will chime in.
RICH

Rich

Thanks for the encouragement, there are three questions/problems with this thread.

Phil

How is your MPG connected? Do you have Brains or Custom Macros?
Hood

Sounds liek a macro thing.. Whats the m6.m1s look like? It may have some code in it to set tool length offsets or something.

When the T0505 is encountered, the offset #5 is applied, so the dro may change to reflect current coordinate. this makes the next move different from what youd assume
depending on whats in offset#5. But if theres any code in the m6.m1s then anything is possible.

  Dont know about homing, the system wont change the motor tuning unless your swapping between metric and english.. I take it the machine is setup in the coordinate system
that you use in the code?

Art

Hood & Art thanks for the help

So far the mpg problem has happened once as i say a completely new install so i haven't knowingly changed any macros.

My main concern is the code i have pasted

It is a screwcutting code it produced a perfect thread i have only shown the beginning and the end to keep the size down.

To run the code i do the following

I change to tool 05 manually

Set the Z Zero position

I run the code "perfect thread"

Now herein lies the problem at the end of the run

The tool dro displays 05 but the axis dro's display the offsets for tool one. This is what was so frustrating finding this problem. How do i know

Because if i now change the tool dro to 01 the axis dro's do not change But if i change them back to 05 the axis dro's change back to the correct position that was commanded in the gcode "N730 X60. N740 Z50."

I did make a video of this but cannot upload it anywhere as it is 3Mb

Now at the end of my code i have a G50 could this be making the problem

Thanks
Phil

Phil:

  It could be. BAsically the program runs ahead of you, so the tool in the dro is simply the last tool commanded in the program usually.
Typing in a new tool to the dro wont change the offset register, youd be better of enter T0505 in the mdi line if you want to swap a tool
to see the effect. I think theres a config item "Remove offsets at end of program " as well, make sure if thats there, it isnt checked. It could
be the program is removing offsets at end of run.

Art

Art

Thanks i will try to find that setting and check it.

I will also change tools from the mdi line from now on.

I have become scared of this machine the last thing i want to see is the tool driving into the chuck

Phil