Re: New Article Posted
Posted by
turbulatordude
on 2006-05-07 21:57:23 UTC
--- In CAD_CAM_EDM_DRO@yahoogroups.com, "ballendo" <ballendo@...> wrote:
pulley on a 200 step motor. that puts me at 2,600 full steps and some
high number of microsteps. I think the driver is 8x ? 20,400
microsteps ?
Assuming the sync pulls the motor to the nearest 1/2 step, we can
assume that anything one microstep closer than 'center' will fall back
and anything one mircrostep past 'center' will fall forward. Center
being that value equally between half steps.
in my case, 1 inch = 1/2600th of an inch or about 0.0003846"
a microstep would be 8 times that or 0.00004807
Now, assuming there are 4 microsteps between each half step, and the
first two will fall back and the second two will fall forward.
assuming further that I have 100 pauses across a part and in every
case, the driver was on 2 microsteps. that would mean the sync mode
would have pulled the position back 2 microsteps each of those 100
times for 200 total microsteps.
with a microstep being 0.000048077 (rounded), then 200 microsteps
would be 0.01" or 10 thou.
the assumptions are;
#1) that the drive actually does pull to the nearest half step when in
sync mode.
#2) that every sync mode would drive from the greatest distance from a
half step
#3) that every sync mode would drive the same way.
#4) that the driver does not automatically recover.
If the sync mode were split 50/50 all errors would effectively cancel
themselves out.
As for my PCB etcher, I move to 1.000" or 4.500" or 0.01" some other
whole number or simple decimal that will be divided evenly by half
stepping. (10 tpi screw on that) in those cases the sync mode would
never have any effect.
Probability would favor that the plus errors and minus errors would
cancel each other out to a large degree.
And, even if one had 1/3 one way, and 2/3 the other, my 200 would drop
to 66. And, if half were one micorstep away and half were 2
microsteps away, then those 66 times is only 99 microsteps or
0.0048077. or just under 5 thou.
5 thou is certainly enough to measure, but in so many cases, I would
never even fall on a microstep that it might be a rare occurance.
Also, if one were drilling a bunch of 80 pin DIP chips or such, the
first hole would be off by a max of 2 microsteps, but the driver would
have the axis pulled to the half step. and I assume that the driver
would never know it was not on that axis, so it would not
automatically add (or subtract) those microsteps. So, if the axis
were to be pulled to the nearest 1/2 step, and the driver didn't know
it moved, then the other 79 pins would fall on the half step.
I am sure there are applications where 5 thou is huge, and others
where is it nothing. I would also assume that some might have many
hundreds of axis stops.
Interesting problem. I would be interested in any empirical data.
Dave
><SNIP>
> >but does not lose any steps when in sync mode. I've been using thisI thought about that today a little. I have a 13 tpi screw on a 1:1
> >setup in half-step mode for months and have not had any problems.
>
> Yes, in HALF STEP mode it will work fine. BUT you WILL lose steps if
> you try to microstep whilst using the sync mode. (or going into and
> out of it).
>
pulley on a 200 step motor. that puts me at 2,600 full steps and some
high number of microsteps. I think the driver is 8x ? 20,400
microsteps ?
Assuming the sync pulls the motor to the nearest 1/2 step, we can
assume that anything one microstep closer than 'center' will fall back
and anything one mircrostep past 'center' will fall forward. Center
being that value equally between half steps.
in my case, 1 inch = 1/2600th of an inch or about 0.0003846"
a microstep would be 8 times that or 0.00004807
Now, assuming there are 4 microsteps between each half step, and the
first two will fall back and the second two will fall forward.
assuming further that I have 100 pauses across a part and in every
case, the driver was on 2 microsteps. that would mean the sync mode
would have pulled the position back 2 microsteps each of those 100
times for 200 total microsteps.
with a microstep being 0.000048077 (rounded), then 200 microsteps
would be 0.01" or 10 thou.
the assumptions are;
#1) that the drive actually does pull to the nearest half step when in
sync mode.
#2) that every sync mode would drive from the greatest distance from a
half step
#3) that every sync mode would drive the same way.
#4) that the driver does not automatically recover.
If the sync mode were split 50/50 all errors would effectively cancel
themselves out.
As for my PCB etcher, I move to 1.000" or 4.500" or 0.01" some other
whole number or simple decimal that will be divided evenly by half
stepping. (10 tpi screw on that) in those cases the sync mode would
never have any effect.
Probability would favor that the plus errors and minus errors would
cancel each other out to a large degree.
And, even if one had 1/3 one way, and 2/3 the other, my 200 would drop
to 66. And, if half were one micorstep away and half were 2
microsteps away, then those 66 times is only 99 microsteps or
0.0048077. or just under 5 thou.
5 thou is certainly enough to measure, but in so many cases, I would
never even fall on a microstep that it might be a rare occurance.
Also, if one were drilling a bunch of 80 pin DIP chips or such, the
first hole would be off by a max of 2 microsteps, but the driver would
have the axis pulled to the half step. and I assume that the driver
would never know it was not on that axis, so it would not
automatically add (or subtract) those microsteps. So, if the axis
were to be pulled to the nearest 1/2 step, and the driver didn't know
it moved, then the other 79 pins would fall on the half step.
I am sure there are applications where 5 thou is huge, and others
where is it nothing. I would also assume that some might have many
hundreds of axis stops.
Interesting problem. I would be interested in any empirical data.
Dave
Discussion Thread
Phil Mattison
2006-05-06 10:54:19 UTC
New Article Posted
lcdpublishing
2006-05-06 14:04:40 UTC
Re: New Article Posted
Dave Rigotti
2006-05-06 15:12:13 UTC
Re: New Article Posted
Phil Mattison
2006-05-06 15:16:53 UTC
Re: [CAD_CAM_EDM_DRO] Re: New Article Posted
turbulatordude
2006-05-06 15:55:53 UTC
Re: New Article Posted
Dave Rigotti
2006-05-06 17:29:17 UTC
Re: New Article Posted
wanliker@a...
2006-05-06 18:50:57 UTC
Re: [CAD_CAM_EDM_DRO] Re: New Article Posted
ballendo
2006-05-06 20:08:11 UTC
Re: New Article Posted
ballendo
2006-05-06 20:33:19 UTC
missed steps going into sync mode? Re: New Article Posted
ballendo
2006-05-07 01:04:56 UTC
Re: New Article Posted
Dave Rigotti
2006-05-07 04:42:40 UTC
Re: New Article Posted
Phil Mattison
2006-05-07 10:01:43 UTC
Re: [CAD_CAM_EDM_DRO] Re: New Article Posted
Phil Mattison
2006-05-07 10:28:55 UTC
Re: [CAD_CAM_EDM_DRO] Re: New Article Posted
Phil Mattison
2006-05-07 10:34:48 UTC
Re: [CAD_CAM_EDM_DRO] missed steps going into sync mode? Re: New Article Posted
ballendo
2006-05-07 18:03:59 UTC
Re: New Article Posted
ballendo
2006-05-07 18:15:42 UTC
Re: New Article Posted
Phil Mattison
2006-05-07 18:41:02 UTC
Re: [CAD_CAM_EDM_DRO] Re: New Article Posted
turyga1963
2006-05-07 21:55:42 UTC
Re: New Article Posted
turbulatordude
2006-05-07 21:57:23 UTC
Re: New Article Posted
wanliker@a...
2006-05-07 22:07:37 UTC
New Article Posted
turyga1963
2006-05-08 00:25:30 UTC
Re: New Article Posted
ballendo
2006-05-08 03:25:17 UTC
Re: New Article Posted
Alan Marconett
2006-05-08 08:31:35 UTC
RE: [CAD_CAM_EDM_DRO] Re: New Article Posted
jeffalanp
2006-05-08 08:34:47 UTC
SLA7062 and Re: New Article Posted
turbulatordude
2006-05-08 08:40:12 UTC
Re: New Article Posted
Codesuidae
2006-05-08 08:50:26 UTC
Re: [CAD_CAM_EDM_DRO] SLA7062 and Re: New Article Posted
Codesuidae
2006-05-08 09:08:39 UTC
Re: [CAD_CAM_EDM_DRO] Re: New Article Posted
turbulatordude
2006-05-08 09:15:26 UTC
SLA7062 technical stuff
wanliker@a...
2006-05-08 10:04:12 UTC
New Article Posted
cncnovice
2006-05-08 11:04:30 UTC
Re: New Article Posted
wanliker@a...
2006-05-08 11:16:32 UTC
Re: [CAD_CAM_EDM_DRO] Re: New Article Posted
cncnovice
2006-05-08 11:37:54 UTC
Re: New Article Posted
Codesuidae
2006-05-08 12:57:24 UTC
Re: [CAD_CAM_EDM_DRO] Re: New Article Posted
turyga1963
2006-05-08 14:13:40 UTC
SLA7062 and Re: New Article Posted
turyga1963
2006-05-08 14:22:17 UTC
Re: SLA7062 technical stuff
turyga1963
2006-05-08 14:23:54 UTC
SLA7062 and Re: New Article Posted
turbulatordude
2006-05-08 14:43:26 UTC
Re: New Article Posted - Moderators warning
turbulatordude
2006-05-08 14:51:32 UTC
Re: SLA7062 technical stuff - supply voltages
turyga1963
2006-05-08 15:01:10 UTC
Re: New Article Posted
turyga1963
2006-05-08 15:16:18 UTC
Re: New Article Posted
turyga1963
2006-05-08 15:21:01 UTC
Re: SLA7062 technical stuff - supply voltages
John Dammeyer
2006-05-08 15:29:03 UTC
RE: [CAD_CAM_EDM_DRO] Re: SLA7062 technical stuff - supply voltages
Paul Kelly
2006-05-08 15:32:39 UTC
RE: [CAD_CAM_EDM_DRO] Re: SLA7062 technical stuff - supply voltages
R Rogers
2006-05-08 16:07:06 UTC
Re: [CAD_CAM_EDM_DRO] Re: SLA7062 technical stuff
turbulatordude
2006-05-08 18:43:15 UTC
Re: SLA7062 technical stuff - supply voltages
ballendo
2006-05-08 19:48:42 UTC
SLA7062 and Re: New Article Posted
ballendo
2006-05-08 20:21:07 UTC
Sync mode musings was Re: New Article Posted
jeffalanp
2006-05-08 20:28:56 UTC
SLA7062 and Re: New Article Posted
ballendo
2006-05-08 22:38:17 UTC
OT SLA7062 and Re: New Article Posted
Lester Caine
2006-05-08 23:14:12 UTC
Re: [CAD_CAM_EDM_DRO] SLA7062 and Re: New Article Posted
wanliker@a...
2006-05-08 23:24:59 UTC
Re: [CAD_CAM_EDM_DRO] SLA7062 and Re: New Article Posted
Mariss Freimanis
2006-05-09 10:11:39 UTC
Re: SLA7062 technical stuff - supply voltages
turyga1963
2006-05-10 22:50:16 UTC
Re: SLA7062 technical stuff - supply voltages
Mariss Freimanis
2006-05-11 06:36:52 UTC
Re: SLA7062 technical stuff - supply voltages
Alan Rothenbush
2006-06-12 12:21:45 UTC
Re: SLA7062 technical stuff - supply voltages