On 18.05.12 23:09, Jon Elson wrote:
The description in the user manual is almost completely incomprehensible.
G10 L20 makes a little bit of sense, G10 L2 makes no sense at all.
The new web page:
On 05/19/2012 06:06 AM, Erik Christiansen wrote:
It scares me that coordinate offsets could be cumulative. Coordinate
offsets (workspaces) should not nest, I believe. I have not read
anything in the doco to say that they do.
That doesn't scare me at all, as long as the documentation is
Erik Christiansen wrote:
Um ... that's always been my problem, when reading the older
documentation. i.e. where the machine is NOW w.r.t. what? Yes, touch
off from the workpiece, and those other references become moot.
It scares me that coordinate offsets could be cumulative. Coordinate
On Saturday, May 19, 2012 05:16:44 PM cogoman did opine:
On 05/19/2012 06:06 AM, Erik Christiansen wrote:
It scares me that coordinate offsets could be cumulative. Coordinate
offsets (workspaces) should not nest, I believe. I have not read
anything in the doco to say that they do.
Hi all,
The setting of the coordinate system (G53-g59.3) is not working the way I
expected, and I am trying to figure out what I am doing wrong. I am running
linuxcnc 2.5, BTW.
After initialization and homing, if I issue:
G53 G0 X0 Y0
It will correctly move to absolute machine 0, 0.
This
Hi all,
Oops, I think I found it (haven't tested yet). I think I am off by one in P
value. I don't understand why it worked the first time however.
Regards,
Eric
Hi all,
The setting of the coordinate system (G53-g59.3) is not working the way I
expected, and I am trying to figure out what I am
Hi all,
Oops again, just a typo on my part. I was using coordinate system 3, but
erroneously referred to it is 2. So the P values are being used correctly
and the problem remains.
Regards,
Eric
Hi all,
Oops, I think I found it (haven't tested yet). I think I am off by one in P
value. I don't
Eric H. Johnson wrote:
Hi all,
Oops again, just a typo on my part. I was using coordinate system 3, but
erroneously referred to it is 2. So the P values are being used correctly
and the problem remains.
Why are you working in the machine coordinate system? I never do that,
it is for
Jon,
I am using the coordinate systems as a means of getting multiple tools
offset in X and Y from each other so they can land on top of each other.
IOW, do a pass with one tool, then apply the offsets of another tool but
otherwise follow the same tool path. For example:
G54 - Null Tool
G55 -
On 18 May 2012 19:38, Eric H. Johnson ejohn...@camalytics.com wrote:
I am using the coordinate systems as a means of getting multiple tools
offset in X and Y from each other so they can land on top of each other.
You _could_ do that with tool offsets in the tool table. (I think).
All tools
Andy,
You _could_ do that with tool offsets in the tool table. (I think).
All tools have spaces for offsets in XYZUVW.
Are you talking about tool.tbl in the config directory? It looks to me like
you can only set tool length
and diameter. Am I missing something? If I could do that this would
Andy,
No, that does seem wrong and strange. I wonder if it is a synch problem,
one part of the code not updating because it thinks nothing has changed on
the basis of an internal value but another part of the code getting the
information from the not-updated section?
I have used this basic
Andy,
I do need to pay more attention to the change log. I waited for 2.5 for this
application specifically for the ability to put named subroutines in their
own folder. I did not realize the tool table functionality had changed in
the previous version.
Thanks,
Eric
Yes.
Which LinuxCNC version
Eric H. Johnson wrote:
Jon,
I am using the coordinate systems as a means of getting multiple tools
offset in X and Y from each other so they can land on top of each other.
IOW, do a pass with one tool, then apply the offsets of another tool but
otherwise follow the same tool path.
I thought
Eric H. Johnson wrote:
Andy,
You _could_ do that with tool offsets in the tool table. (I think).
All tools have spaces for offsets in XYZUVW.
Are you talking about tool.tbl in the config directory? It looks to me like
you can only set tool length
and diameter. Am I missing
On 19 May 2012 02:40, Jon Elson el...@pico-systems.com wrote:
Anyway, the G10 L2 Px adds an offset from the CURRENT machine position,
Are you sure about that? That isn't what the docs say. G10 L2
shouldn't consider the current position at all, it should simply
define the offset between machine
andy pugh wrote:
On 19 May 2012 02:40, Jon Elson el...@pico-systems.com wrote:
Anyway, the G10 L2 Px adds an offset from the CURRENT machine position,
Are you sure about that? That isn't what the docs say. G10 L2
shouldn't consider the current position at all, it should simply
17 matches
Mail list logo
