Today I made a simple 1 wire probe so I can probe a surface for engraving, pcb
milling and for tool offset contact plate. I was playing around in the MDI with
G38.2 and I have some questions.
The tool drives into the plate and of course goes through it (I mean, bends it,
flexible 10mil sheet) a
I am writing some code to mill solder paste stencils. I would like to use a
probe to map the surface for possible unevenness in the surface before milling.
Since the gcode is generated by a program I have two methods I see.
1. (obvious one) probe first to a log file, feed into the program which
John Kasunich wrote:
> It does not introduce a delay.
>
> It uses the velocity between the last two edges to predict the position
> as time moves on, until the next edge arrives, at which point it uses
> that edge to correct any error in the prediction.
>
> Below is a halscope plot from when I was
Jon Elson wrote:
> Andy Pugh wrote:
>> Is there any reason not to use position-interpolated by default?
> There might be. I don't know how position-interpolated works, but I
> assume it might
> introduce a delay in the position reports.
It does not introduce a delay.
It uses the velocity betwe
Michael Haberler wrote:
>
> stepgen just does what axis tells it to do:
> http://mah.priv.at/cgi-bin/viewvc.cgi/emc-syncmove/pos-cmd-steprate.png?revision=1.1&root=CVS&view=markup
>
> the wobble is already in axis.2.motor-pos-cmd so that takes stepgen
> out of the picture IMHO
>
Well, the dbg
Andy Pugh wrote:
> 2009/10/22 Michael Haberler :
>
>> yes - I ran into the problem when switching to hm2 which doesnt
>> currently provide position-interpolated
>>
>>
>
> Which is an interesting point. It seems that a hardware quadrature
> counter is likely to be counterproductive if you ha
Am 22.10.2009 um 20:04 schrieb Jon Elson:
> ...
> limit, and then the system becomes violently unstable. This is all
> just
> guessing from too little info,
> hopefully we can get some plots of other signals from the stepgen to
> see
> in more detail what is
> happening inside.
>> Also note
2009/10/22 Michael Haberler :
>
> yes - I ran into the problem when switching to hm2 which doesnt
> currently provide position-interpolated
>
Which is an interesting point. It seems that a hardware quadrature
counter is likely to be counterproductive if you have a low-count
encoder.
With a softwa
Am 22.10.2009 um 12:21 schrieb Andy Pugh:
> 2009/10/22 Jon Elson :
>
>> Good hypothesis and data taking! So, it seems the problem is the
>> encoder counter sees
>> a zero velocity between actual encoder counts, and tells the slaved
>> axis
>> to stop NOW! Then a
>> count comes in, and it says
I'm confused by your question, so my answer may be off the mark.
In my configuration for a linear axis, I have INPUT_SCALE set to 2048, that
is, 2048 steps per millimeter.
You need to set that up first for rotary axis, the number of steps per
degree. You mention 120,000. Is that 120,000 steps p
Andy Pugh wrote:
An alternative might be to keep things much as they are, but to have a
parameter in the G-code for how much "run up" it has. It then becomes
a somewhat simpler trajectory planner issue to get to the thread start
at the right speed next time the index comes round on the unloaded
s
Andy Pugh wrote:
> 2009/10/22 Jon Elson :
>
>
>> Good hypothesis and data taking! So, it seems the problem is the
>> encoder counter sees
>> a zero velocity between actual encoder counts, and tells the slaved axis
>> to stop NOW! Then a
>> count comes in, and it says MOVE NOW! Yes, I can see
>> This caused me to wonder... How many encoder pulses per inch does a
professional CNC machine use.
My lathe - a commercial "hard turn" machine that I bought from Timken only has
2450 pulses per inch of travel on both axes.
It was originally setup to turn semi hard bearing races prior to heat
Good idea, I have been thinking about the tool table being in the data
base for a while. Fully automated manufacture here we come.
Dave Caroline
--
Come build with us! The BlackBerry(R) Developer Conference in SF, CA
is t
2009/10/22 Jon Elson :
> Good hypothesis and data taking! So, it seems the problem is the
> encoder counter sees
> a zero velocity between actual encoder counts, and tells the slaved axis
> to stop NOW! Then a
> count comes in, and it says MOVE NOW! Yes, I can see this is a definite
> problem.
Hi,
I've written a simple python script for Axis, which allows you to retrieve your
gcode from a mysql database.
If anybody is interested in this, the details are on my site at:
www.andyshelley.co.uk/emc/index.php.
I've also posted this link on the linuxcnc forum.
Thanks,
Andy.
-
Hi,
Is there any way of multiplying or dividing feedrate? On the
little gantry system I have just set up the rotary axis is
driven by a microstepping stepper driving a worm and wheel
and so, at the moment, G0 corresponds to a feedrate of
around 120,000! I want to maintain the input accuracy of
17 matches
Mail list logo
