Hello Guest it is July 11, 2020, 11:51:10 PM

Author Topic: Mach did again!  (Read 21433 times)

0 Members and 1 Guest are viewing this topic.

Re: Mach did again!
« Reply #20 on: September 29, 2010, 04:46:33 PM »
It happened again. I just finished a toolpath, waiting to change out tools, had a phone call that I had to take. I changed the tool, zeroed manually, pushed Cycle Start. the machine runs off course, but the DROs read what the last location was before the M6 callout. Here's abit of the code where this happened:

N22450G1X-2.9990Y0.9860Z-0.4800
N22460G1X-3.0000Y0.9745Z-0.4800
N22470G1X-3.0000Y-1.0774Z-0.4800
N22480G1X-2.9990Y-1.0889Z-0.4800
N22490G1X-2.9957Y-1.1057Z-0.4800
N22500G1X-2.9924Y-1.1168Z-0.4800
N22510G1X-2.9884Y-1.1250Z-0.4800
N22520G00X-2.9884Y-1.1250Z0.2500
N22530T203M6
N22540 (Tool: End Mill {0.25 inches})
N22550G43H203
N22560S2500M03
(Profile .250 End Mill)
()
N22590G00X0.0084Y0.1124Z0.2500
N22600G1X0.0084Y0.1124Z-0.2589F10.0
N22610G1X0.0432Y0.1074Z-0.2589F40.0

Offline Hood

*
  •  25,846 25,846
  • Carnoustie, Scotland
    • View Profile
Re: Mach did again!
« Reply #21 on: September 29, 2010, 04:49:55 PM »
So the machine moved but the DROs didnt?
Hood
Re: Mach did again!
« Reply #22 on: September 29, 2010, 04:57:25 PM »
The DROs read:

X  -2.9884
Y  -1.1250
Z   0.2500


I changed the tool and zeroed the tool, the axis read the same as above except for the Z.

I push Cycle Start and the table moves away from where it is supposed to. I stopped the program and hit Go To Zero, it is nowhere near being 0,0.

One thing I thought of and I am assuming that it is right, but in General Configuration I read:

Constant Velocity is on
Distance mode is in Absolute
IJ Mode is in Inc

Is this correct?

Offline Hood

*
  •  25,846 25,846
  • Carnoustie, Scotland
    • View Profile
Re: Mach did again!
« Reply #23 on: September 29, 2010, 05:10:23 PM »
So when the table was moving away were the DROs showing that movement?
Can you sip and attach your two M6 macros.

All these settings are fine or should be depending on your code but from what you have shown they are fine.
Hood
Re: Mach did again!
« Reply #24 on: September 29, 2010, 05:20:53 PM »
Yes the DROs were showing the movement, but they continued "counting" from where the were X  -2.9884, Y  -1.1250.

I tried to do a driver test and I am told that it is Pulsing Too Fast.

Re: Mach did again!
« Reply #25 on: September 29, 2010, 05:28:57 PM »
Here are the M6 files
Re: Mach did again!
« Reply #26 on: September 29, 2010, 08:28:27 PM »
Disabling the ATZ function and macros did nothing.

Offline Hood

*
  •  25,846 25,846
  • Carnoustie, Scotland
    • View Profile
Re: Mach did again!
« Reply #27 on: September 30, 2010, 03:02:07 AM »
I am getting confused, one minute the DROs are the same the next they are moving.
Really I think you have to be very methodical in noting down what you see and describing it when things go wrong. What you need to note is where the DRO and Toolpath say the axis is and whether or not it is actually there. Forget the return to zero as all that is telling you is you have lost position, we need to try and work out why you have lost position.

As for the pulsing too fast, was Mach running at the time?
Hood

Offline BR549

*
  •  6,932 6,932
    • View Profile
Re: Mach did again!
« Reply #28 on: September 30, 2010, 10:23:09 AM »
1 question,  When this last happened and MACH wondered off, did you see the wandering off in the toolpath display as well? AND did the dros show that it had wondered off the programed toolpath?

Have you tired to reload a known good backup of the XML?

IF you do not have one build a brand new XML from scratch using all the setup info that you have in your old one.

IF that does not work then do a completed reload of mach.  BUT FIRST document precisely how it happens NEXT TIME it does it

IT is important when testing that you do not jump around doing a lot of different things at the same time. ONLY a methodical test approach will find your problem. NOTES as Hood said LOTS of noted describing each step you take. AND do them them one step at a time.

You explanation is somewhat all over the place as Hood said.  Settle down and we can get to the bottom of the problem.

(;-) TP
Re: Mach did again!
« Reply #29 on: September 30, 2010, 12:47:34 PM »
1 question,  When this last happened and MACH wondered off, did you see the wandering off in the toolpath display as well?


I did not notice this.



AND did the dros show that it had wondered off the programed toolpath?


No, they showed exactly what the G Code stated at the time of the tool change



Have you tired to reload a known good backup of the XML?


No I haven't




IF you do not have one build a brand new XML from scratch using all the setup info that you have in your old one.

IF that does not work then do a completed reload of mach.  BUT FIRST document precisely how it happens NEXT TIME it does it

IT is important when testing that you do not jump around doing a lot of different things at the same time. ONLY a methodical test approach will find your problem. NOTES as Hood said LOTS of noted describing each step you take. AND do them them one step at a time.


I typically change one thing at a time

You explanation is somewhat all over the place as Hood said.  Settle down and we can get to the bottom of the problem.


I think what the problem is I am not saying what I exactly mean. Or this is a miscommunication in the question vs. the answer.






(;-) TP
« Last Edit: September 30, 2010, 12:49:05 PM by ranchak »