I am trying to setup some subroutines to do tool length and touchoff
calculations. Where can I see the #parameters while the system is running.
I am storing a value in say #1000 and then I want to use it later in
another sub. I am not sure if my data is correct as I keep on ending up
above the
Hi Marius!
On 12/30/2013 09:43 AM, Marius Liebenberg wrote:
I am trying to setup some subroutines to do tool length and touchoff
calculations. Where can I see the #parameters while the system is running.
I am storing a value in say #1000 and then I want to use it later in
another sub. I am
Thanks Phillip I will try that.
On 2013-12-30 11:21, Philipp Burch wrote:
Hi Marius!
On 12/30/2013 09:43 AM, Marius Liebenberg wrote:
I am trying to setup some subroutines to do tool length and touchoff
calculations. Where can I see the #parameters while the system is running.
I am storing
On Monday 30 December 2013 06:01:46 Marius Liebenberg did opine:
I am trying to setup some subroutines to do tool length and touchoff
calculations. Where can I see the #parameters while the system is
running. I am storing a value in say #1000 and then I want to use it
later in another sub. I
Hi all!
Maybe you remember my question of a few weeks ago about a more flexible
way to transform the coordinates in a G-code file:
http://sourceforge.net/mailarchive/forum.php?thread_name=528A6D98.7080208%40hb9etc.chforum_name=emc-users
My decision was then, to do most of the transforms in
Hi Philipp,
a bit of guts first:
Configs with a UI which sports preview actually have two interpreters
there's one in the milltask process - this is the 'real one' which drives the
machine, and which you've been talking to with your sample program
then there's a 'preview interpreter' in the UI
in principle those two are unrelated ; of course they should work on the same
ngc program. UI's deal with that by telling the preview interpreter to
generate preview, and tell milltask to actually execute the program driving
the machine.
what happened with your program: you talked to
Hi Michael, hi Chris!
On 12/30/2013 07:33 PM, Michael Haberler wrote:
Hi Philipp,
a bit of guts first:
Configs with a UI which sports preview actually have two interpreters
there's one in the milltask process - this is the 'real one' which drives the
machine, and which you've been
On 29 Dec 2013, at 20:40, Charles Steinkuehler char...@steinkuehler.net wrote:
LinuxCNC has a run in place feature, from the directory where you
built the code, just run scripts/rip-environment and you'll be setup
to run the build in that directory. Different shell windows can be
setup to
Thanks again for the suggestions. I feel like I am making headway.
However, I can't seem to figure out how to set one of the Stepgens to
velocity mode since they are all created together via some pru_generic.bin
file.
Is there a way to pass this argument to this bin file or is there a way to
My step/dir generators are modeled after the hostmot2 components and
generally have identical pins, ports, and behavior (at least that was my
goal), so you control velocity or position mode with the control-type
pin, ie:
hal_pru_generic.stepgen.00.control-type
See also:
11 matches
Mail list logo
