On Sunday, February 05, 2012 02:42:38 AM Erik Christiansen did opine:
On 04.02.12 18:04, gene heskett wrote:
What would you folks use when you need an insulated pallet?
If nothing out of the junkbox will do, I'd fish out my old tin of
automotive bog and make up a few suitably sized slabs.
Hi Peter,
I just figured out how to get it working again.
The patch seems to be based on a snapshot of the master branch
somewhere at the end of January.
On my machine I can reproduce the (very nice) results with these commands:
git checkout dcbaa105aaa5494ba5eea296ca66df893bd5c9b6 -b
sure, but either way you look at it: if there's a language change, there still
be a need for recognizing the old syntax, either for in-place compatibility or
external automatic conversion
-m
Am 04.02.2012 um 22:25 schrieb Kenneth Lerman:
The use of matching labels to resolve ambiguity was
On 2/4/2012 4:29 PM, Kenneth Lerman wrote:
I end up doing this all the time since my current small mill is limited
to 16 X travel. However I define Y with respect to the upper jaw of
the vise so all I have to do is slide the part in x to get the dowel
pin aligned.
I'll bet that Stuart
Hi Michael,
Thank for the hints. I will soon try it out and report about the success.
I'm using a program called ProfiliPro from Stafano Duranti
(http://www.profili2.com/eng/), which produces quite accurate g-code and is
easy to handle. Unfortunatly it's not free, but the 60€ are worth for it.
I'm bringing up my mini-mill and have encountered a weird problem: I'm trying
to use pins 10, 11 12 on the printer port as limit switch inputs for X, Y, Z
axes, respectively, but the pins are acting like outputs. The limits switches
are active high, with ether voltage dividers or diodes in
I must admit I've I've watched this thread unfold with a bit
of apprehension. Certainly the current direction has evolved to the point
where the result will likely not be usable for my purposes. I don't see a
way of using a flex/bison-based parser from python apart from native
bindings, so in
For the relatively smaller edge case of those wanting to
hand-code sophisticated machine control, gcode (even the LinuxCNC flavor)
For a lot of us hand coding is not an edge case, the available free
open source cam tools simply do not cater for anything over 3 axis
milling. which is just a subset
On Sunday, February 05, 2012 01:28:12 PM N. Christopher Perry did opine:
I'm bringing up my mini-mill and have encountered a weird problem: I'm
trying to use pins 10, 11 12 on the printer port as limit switch
inputs for X, Y, Z axes, respectively, but the pins are acting like
outputs. The
I am using AXIS 2.4.7 (caption says 2.4.6)
At startup jog speed on axis A is 2094 deg/min and maximum is 21600. More
suitable in my case would be default 100 max 2000 or so. How do I change the
jog speed defaults?
I have also tried to change axis 3 in the .ini to TYPE = LINEAR. This
On Sat, Feb 4, 2012 at 11:39 AM, Martin Patton mart...@gmail.com wrote:
This is probably an easy one but I'm stuck. How do I stop the program,
reposition the workpiece and restart the program without losing the
spacing?
Thanks,
Marty
as stated, it's really easy because you just start a
I see no need for anything pythonesk in machine control. This just
adds an obscure level of abstraction from the real machine.
I too wrote a gcode generator for some of my standard shapes but found
it was more elegant to do it in gcode
as I could use sensible(ish) variable names. why enter
Another cheat is mount a rotary table off centre (even outside the
normal xy envelope)
and then you can make larger parts, ok the gcode is not so simple
unless you are making a gear.
Dave Caroline
--
Try before you buy =
On Sunday, February 05, 2012 02:16:37 PM Lars Andersson did opine:
I am using AXIS 2.4.7 (caption says 2.4.6)
At startup jog speed on axis A is 2094 deg/min and maximum is 21600.
More suitable in my case would be default 100 max 2000 or so. How do I
change the jog speed defaults?
Thanks Gene,
change in [TRAJ] was the cure.
From your post:
[AXIS_3]
TYPE = ANGULAR
HOME = 0.0
MAX_VELOCITY = 30.0
MAX_ACCELERATION = 200.0
STEPGEN_MAXACCEL = 300.0
Not immediately obvious, why is MAX_VELOCITY used here, not
MAX_ANGULAR_VELOCITY ?
It is similar in my .ini
// Lars
gene heskett wrote:
This board claims excellent speed, as in 10ns propagation delays thru the
opto stuffs. That seems rather fast for opto's, and I haven't measured it
although I have the scope to do it with.
I don't believe it! If they are really opto-isolators and not some other
Am 05.02.2012 um 19:07 schrieb Scott Hasse:
I must admit I've I've watched this thread unfold with a bit
of apprehension. Certainly the current direction has evolved to the point
where the result will likely not be usable for my purposes. I don't see a
way of using a flex/bison-based
On Sun, 2012-02-05 at 12:41 -0500, N. Christopher Perry wrote:
I'm bringing up my mini-mill and have encountered a weird problem:
I'm trying to use pins 10, 11 12 on the printer port as limit switch
inputs for X, Y, Z axes, respectively, but the pins are acting like
outputs.
The parallel
On Sunday, February 05, 2012 08:35:42 PM Lars Andersson did opine:
Thanks Gene,
change in [TRAJ] was the cure.
From your post:
[AXIS_3]
TYPE = ANGULAR
HOME = 0.0
MAX_VELOCITY = 30.0
MAX_ACCELERATION = 200.0
STEPGEN_MAXACCEL = 300.0
Not immediately obvious, why is MAX_VELOCITY
On Sunday, February 05, 2012 08:41:06 PM Jon Elson did opine:
gene heskett wrote:
This board claims excellent speed, as in 10ns propagation delays thru
the opto stuffs. That seems rather fast for opto's, and I haven't
measured it although I have the scope to do it with.
I don't believe
Yes, like a jig for cutting a guitar fretboard for instance.
Cut twelve frets, move the fretboard, cut six more.
I think I just need to make a spacer.
Thanks for the ideas.
--
Try before you buy = See our experts in
On 05.02.12 18:35, Dave Caroline wrote:
For the relatively smaller edge case of those wanting to
hand-code sophisticated machine control, gcode (even the LinuxCNC flavor)
For a lot of us hand coding is not an edge case, the available free
open source cam tools simply do not cater for
Greetings Guys;
2 questions actually:
1. What is the schedule saying about the renaming of this list to
linuxcnc-users@etc?
2. I apparently am having trouble understanding the G92 family docs, which
state:
G92 makes the current point have the coordinates you want
Thanks Kirk,
I did as you suggested, and while I was at it I measured the series current
when shorted and found that it was ~2mA. My pulldowns were in fact too high
an impedance. I dropped them to ~300 ohms and everything is now working as
expected.
N.C.
On Feb 05, 2012, at 05:56 PM, Kirk
List:
Does anyone know of a Linuxcnc user that has implemented a working
rho-sigma machine, eg. one linear axis and one rotary axis. The kins
should not be difficult and it should prove to be quite stiff.
Dave
--
On Sun, 5 Feb 2012 21:49:44 -0800
dave dengv...@charter.net wrote:
List:
Does anyone know of a Linuxcnc user that has implemented a working
rho-sigma machine, eg. one linear axis and one rotary axis. The kins
should not be difficult and it should prove to be quite stiff.
Dave
Yes,
I was very seriously thinking about a machine like that, but with the
rotary positioned at an angle.
and an extra linear axis.
We are waiting for the customer to make up his mind.
All problems I saw was kinematics which as you said are not all that
involved.
And perhaps some python script to
Hi Guys;
I think after a splitting headache from 3 hours of reading docs (too damned
sweet too according to my sugar meter), I may have a better idea for the
offsets.
1. Use tholefinder.ngc to locate home dead in the center of that brass tube
which is nominally -0.2X and +0.1Y from the left
On Mon, 2012-02-06 at 05:08 +, N. Christopher Perry wrote:
Thanks Kirk,
I did as you suggested, and while I was at it I measured the series
current when shorted and found that it was ~2mA. My pulldowns were
in fact too high an impedance. I dropped them to ~300 ohms and
everything is
29 matches
Mail list logo
