开云体育

----- Original Message -----
From: ballendo
To: mach1mach2cnc@...
Sent: Friday, August 06, 2004 1:46 AM
Subject: [mach1mach2cnc] Re: As the sun goes down... de de deedee de de deedee (a new sort of cnc "Zone")


List,

Can somebody using a slow (~500mhz) computer, preferably with Win2k
PLEASE try these(previously posted) files, and tell me your
results?!?!

Art,

SOMETHING is broken. Now if it's my drives, then how do you account
for accurate movement when the ONLY thing changed is the helix lead,
by changing the z departure value...?

Seems to me that logically if one "lead" WORKS and one .001 different
is erratic, and one .001 from THAT fails completely; then WHAT is
different as far as the drive is concerned???

Could you put a scope on YOUR Z axis step AND dir output and run
these files again (just the three mentioned above; described
as "fails", "erratic", and "works" in the previous post,near the ned
of th elist, as I dialed into the "problem". So I thought...)

Do you find it at all interesting that the Bzzt of steps is AT the
transition from one move to the next?(which is also 0,0,0 in this
case.) And the additional step or two "seems to be at the quadrant
changes??? How does the DRIVE know anything about quadrants? (dir
change. That's its only clue.) As for plane origins, it has NO clue.

So what about a DRIVE would cause a sputter of steps in Z at a dir
change in XY??? More importantly, what is changed for the DRIVE when
the lead goes up by only one thousandth--which will only be 2 extra
steps per complete circle!!!

A certain number of steps works, ONE more is erratic, and TWO more
fails to move the Z AT ALL...

So let's again say that these ARE slow drives. The XML I'm sending
has the step length set at 15 (but most testing was at 12, and the
pre change at 6.

I've lost 6 days on this so far. I keep thinking I'll come here and
see an "I found it B!" But alas, Not tonight either...

Ballendo (Feeling tired, frustrated, and defeated)

BTW, today I tried larger helical moves, and had more relatedly
interesting results. Not sure at this point if its worth posting...
in a separate post.

BUT, CV from Arc-to-Arc IS broken in BOTH Enh and 4.0 modes in RC8.
There's a pause at the intersection between each helical circle--
right where the BZZT happens...


--- In mach1mach2cnc@..., Art <fenerty@a...> wrote:
> B:
>
> > The way I can make or break a file is to change the ratio of the
> > diameter to the z departure, as suspected...
>
> Good, maybe I can repeat it...
>
> > (THERE IS ABSOLUTELY NO WAY TO SEE THIS PROBLEM UNLESS YOU HAVE A
> > MACHINE HOOKED UP AND RUNNING.)
>
> I've been testing all these on arunning machine. The Z follows
exactly as
> it should on mine...
>
> >
> > (250mod11-fails)
> > g90
> > (xy hole position here)
> > g01z0f5 (move to material surface, set F/R)
> > G02x-.062y0i-.031j0(half circle move to edge of hole)
> > g02x-.062y0i.062j0f5z-.042
> > g02x-.062y0i.062j0z-.084
> > g02x-.062y0i.062j0z-.126
> > g02x-.062y0i.062j00z-.168
> > g02x-.062y0i.062j0z-.210
> > g02x-.062y0i.062j0z-.210
> > g02x-.0620y0i.062j0z-.210 (ensure complete cutting, flat bottom
hole)
> > g02x0y0i.031j0z.1 (helical move out of hole,away from hole wall)
> > M30
> > (end of file )
> > :::::::::::::::::::::::::::::::
> > Fails in all helixes--except last, as noted above
>
>
> Nope. Runs fine here. All movement, X,Y and Z move at correct
rate and
> correct distance.
>
>
> All my tests were run in CV mode enhanced pulse train at 25Khz.
Can't find
> any trouble at all. I'll tell you though,
> that I cannot see a situation where the pulses can come too soon or
too late
> without the TPD showing it on update.
> It is a separate entity of its own for that exact reason. It has no
idea
> what is planned or even what your doing, it is simply drawing the
position
> of
> how many pulses have gone out. It sounds to me like somehting else
is going
> on here, if the display is drawing a helix, it simply is not
possible for
> the
> steps not to be following the output or you would see sporatic
results on
> the update screen. On the other hand, this is CNC and the
impossible is
> sometimes possible.
>
> The user who claimed no Z movement while the DRo was moving is
> undoubtably having some sort of tuning trouble on his axis, like he
saidm it
> jams at times while moving, so it probably is more related to the Z
load.
> (This happens alot on Z's only for obvious reasons. Your XML will be
> interesting to see if its repeatable then....
>
> Later,
> Art


Yahoo! Groups Sponsor
ADVERTISEMENT





------------------------------------------------------------------------------
Yahoo! Groups Links

a.. To visit your group on the web, go to:


b.. To unsubscribe from this group, send an email to:
mach1mach2cnc-unsubscribe@...

c.. Your use of Yahoo! Groups is subject to the Yahoo! Terms of Service.