Stuart - Thank you for starting this thread and posting your kinematics
calculations. I hadn't delved into the kinematics aspect of EMC2, but
reading through your calculations the proverbial light-bulb went on and how
positioning is computed and achieved makes a lot more sense to me now. Once
Greg,
I probably wouldn't yet take this work as the definitive kinematics. :)
It is a work in progress and learning (OJT).
having some fun now
Stuart
On Sun, Dec 14, 2008 at 8:38 AM, Greg Michalski
emc2usrl...@distinctperspectives.com wrote:
Stuart - Thank you for starting this thread and
Up until now, I have been using AC2GC for gcode generation. While this is
ok, it gets tedious when I am generating multiples of a single part. I have
reviewed the Gcode manual numerous times and cannot get my mind wrapped
around the method for doing this. I reckon something along the line of a
BRIAN GLACKIN wrote:
For simplicity, can someone show a looping routine to cut out a square 1 X
1 path (not worried about tooling offsets) then skip 1/2 on the Y axis and
repeat. Once it reaches the end of the Y axis (24 in my case), I want it
to index down the X axis and reverse on down the
Here's a program that does something like what you asked for.
You might also be interested in the file 'interesting-subroutines.ngc', which
should be installed in the examples directory.
Jeff
(- CUT HERE --)
O100 sub (square [x0] [y0] [z0]
Seb,
THanks for the link. I checked the site and I cannot seem to access any of
the articles due to subscription requirements. Perhaps in the future I will
explore this avenue, bit for the time being, Christmas preparations preclude
spending on this.
snip
Jeff,
Thanks for the snippet of code.
You might also look at the g code generators here
http://wiki.linuxcnc.org/cgi-bin/emcinfo.pl?Simple_EMC_G-Code_Generators
and take a look at
http://www.linuxcnc.org/docview/html//gcode_main.html#sub:G92,-G92.1,-G92.2,
http://www.linuxcnc.org/docview/html//gcode_main.html#cha:O-Codes
John
You can also view that file, useful-subroutines.ngc, from the comfort of an
internet-connected computer:
http://cvs.linuxcnc.org/cvs/emc2/nc_files/useful-subroutines.ngc?rev=1.4;content-type=text%2Fplain
Jeff
--
You can grab a 'cheap' KVM from ebay, and a dumpster box to have a 'test
system' on your desk.
It may not be graceful, but if you can have the box in the workshop
running, you can use VNC on
your desktop inside to view what is going on there. I wouldn't really
CUT anything with it that way,
I'm pleased to announce the next release of the emc 2.2 series, emc
2.2.8. This release contains a fix for a rare bug that caused incorrect
movement for G2 and G3 arc moves, as well as a few other things.
The new packages are now available for Ubuntu 8.04 Hardy Heron in the
package repositories.
Stuart Stevenson wrote:
Gentlemen,
which style of computation would run faster in the kinematics file?
this:
va1=atan(askew1)
va2=atan(-bskew1)
snip
or this:
acomp=asin(sin(acmd))-(((cos(acmd))*(sin(-bcmd)))*$
(tan((atan(-bskew1))*(cos((atan(-bskew1)/$
snip
count up
Given today's PCs, for all but the most hard-core numbercrunching, you
are better off optimizing for readability. Don't do obviously bad
things like computing the same value three times, but in general, if you
are doing closed form math that doesn't involve loops or iteration, it
will be very
Stephen Wille Padnos wrote:
I was in the middle of writing a similar statement, with some general
instructions on writing a test program, when I decided to just write the
test program instead :) I found that the first version runs 1,000,000
loops in about 0.5 seconds (on a 2.2 GHz Core 2
BRIAN GLACKIN wrote:
Seb,
THanks for the link. I checked the site and I cannot seem to access any of
the articles due to subscription requirements. Perhaps in the future I will
explore this avenue, bit for the time being, Christmas preparations preclude
spending on this.
it won't be
I finally got some time to play around with this. Simply changing the
read_x function to halve the X axis seems to work. I had a look through
a Fanuc lathe manual and that appears to be exactly what they do. Axis
already shows the X radius and diameter so it doesn't really need
changing. DTG
Gentlemen,
From the looks of some of the current kinematics files I will
assume two things:
1: the 5 axis tool length compensation is handled outside the kinematics file.
2: the pivot length compensation is handled inside the kinematics file.
Unless otherwise advised I will construct my kins
I am using the Mesa 5i20/7i33 system to retrofit my knee mill. I just finished
installing a 500 line (2000 ppr) encoder on the spindle, it is connected to the
Enc03 quadrature inputs on P2.
My timing settings in my ini file are:
BASE_PERIOD =35000
SERVO_PERIOD =
Tom wrote:
I am using the Mesa 5i20/7i33 system to retrofit my knee mill. I just finished
installing a 500 line (2000 ppr) encoder on the spindle, it is connected to the
Enc03 quadrature inputs on P2.
My timing settings in my ini file are:
BASE_PERIOD =35000
Unless you're
Stephen Wille Padnos spad...@... writes:
I think there's something off in your calculations :)
2000 counts/rev * 3000 revs/min = 6,000,000 counts/minute
Dividing by 60 gives 100,000 counts/second at 3000 RPM, at 6000 RPM it
would be 200 kHz.
Stephen,
I forgot to mention that I have a
19 matches
Mail list logo
