>>The same code I tested 2x and worked
fine. Then on tool change it start to
>>hit the z-limit switch
again
This is almost textbook for a system with Z axis trouble. When
the axis
drives into the material, it struggles and steps get lost, this
causes a
most
annoying and confounding type of problem, in the air all
is fine, in
material you hit the Z upper limit switch over
time.
The test for this is simple, run a program that drives the Z up
and down
several times and moves in the X after each Z up and down. Run
this in the
air 10 times, then see if Z has lost anything. Then run it in
material 10
times, where the Z has to cut the material on each downward
plunge. How
often out of 10 times is it out of position in the Z at end of
program?
If the AIR run is clean, and the material run is not.. you
have a problem
with your Z.. Sometimes its the speed is too high on the
retract, meaning
your Z tuning is set too high. ( Personally, when seeing
this type of
problem my first move is to lower the Z max tuning speed by
50% as a test.
If that doesnt fix
it I then turn down the Z plunge rate
in the GCode by 50% to see if that
fixes it.. I rarely get further than
those two tests before the issue shows
itself.
If GCode runs
properly in the air... and doesnt in material, the problem
in 95% of cases
is the machine, not the GCode or Mach3. Ive seen this
error literally
thousands of times over the years, the problem....and its
ensuing
frustration remains the same. :) , Mach3 still has many bugs, most
known,
but it runs the same from run to run in 99.999% of cases.. so in your
case, Im betting on a mechanical / tuning
issue...
Thanks,
Art
----- Original
Message -----
From: charles Fellows cfellows49@...
[mach1mach2cnc]
To: mach1mach2cnc@...
Sent:
Tuesday, February 17, 2015 8:17 AM
Subject: Re: [mach1mach2cnc]
Support
Andre,
I am sorry you are still having problems. It
appears your issue is tied to
tool height compensation. I suggest you
experiment with limited code until
it is worked out. When I was learning I
used a cardboard box as my table
height so I could change tools and have
time to hit E-stop before I struck
the bed if something was
wrong.
I have observed in your discussions you include diameters. I
suggest until
you work this out you forget diameters and only pay
attention to lengths.
The easiest way to have the problem you are
describing would be to be using
the offsets screen incorrectly. Are you
using the offsets screen at any
time?
I have an hour or so if you
are available now. Please describe how you have
determined tool length,
how you have set your lengths into the tool table,
and how you have
numbered your tools.
Charlie.
On Tue, Feb 17, 2015 at 6:59 AM,
'Andre Schoonbee' andresch@...
[mach1mach2cnc] <mach1mach2cnc@...>
wrote:
I do not know if I am allowed to post a RFQ/RFP on this forum
but, I am at
the end of the line ¨C for some reason Mach is working on my
nerves and seems
to get a kick out of it.
When using Vectric Aspire
and generate code it works perfect.
But then with the help of the guys
form Cabinet Vision, the code is acting
weird. This yesterday and this
morning, O was doing a test run of g-code and
it worked fine, it sliced
the air like butter ¨C each line executed perfect.
I then restarted my
machine again to make sure no memory or setting issue
can creep in to
cause a problem and started the real cut of a MDF sheet -
cutting a 4
drawer floor cabinet. The same code I tested 2x and worked fine.
Then on
tool change it start to hit the z-limit switch again.
I need someone
that know mach well and also can detect why the g-code is
causing this.
This person should preferably be willing to do remote support.
To make
sure there is no setting error om my machine, give advice in the
steps I
follow, maybe provide customized scripts if needed, and then most
important, help me to identify why the code on mach3 works and then all of
a
sudden does not work without anything changed.
This is really
urgent
This email has been checked for viruses by Avast antivirus
software.
