Hello Guest it is March 29, 2024, 01:35:56 AM

Show Posts

This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.


Messages - nyholku

Pages: 1 2 »
1
Thanks, that was a new idea to me!

2
Thanks Rich,

I do not understand why the annoyed tone in your response.
I think I've been courteous  and not a bit disrespectful towards any one.
Sorry about my lack of communication skills, English is not my native language.

And thank you very much for the confirmation that this cannot be done with G-code,
this is what Tweakie's answer implied and what I guessed from lot of reading
and googling. Just wanted to know if I had missed anything.

Fair point that ZERO button can do different things, I just used that as an example
to explain (poorly it seems) what it was I wanted to know.

Thanks again, Kusti



3
Hi Tweakie,

yes you did and I believe you and appreciate that but since Rich volunteered I thought maybe he had something to add/contribute but I seem to have difficulty in getting through to him with my original question.

wbr Kusti

4
Thanks Rick,

I'm not really making myself clear.

My question is simply how: how can I do the equivalent of pressing the ZERO button with G-code?

wbr Kusti



5
Thanks Rich,

I think I'm have a fair (I hope) understanding of the  coordinate systems.
And I've read both Mach3 and Mach4 manuals and I do not see how G10
can be used to get the same effect as pressing ZERO button that is next to the DROs.

Like I tried to explain, this is what I thing happens when you press ZERO:
"Assume abs machine position X=100, suppose my current work offset set is 1 (G54),
the if I press ZERO this will set X of work offset 1 to 100 and the X DRO reads now 0, correct?"

If that is not what happens I'd be happy to be educated (of course above assumes all
other offsets are zero).

So to get that effect what should I do?

In LinuxCNC  (according to manual, have no experience there) this would be achieved
for X-DRO with:

G54 G10 L20 P1 X0

Mach3 manual does not mentio G10 L20, Mach4 manual says G10 L20 is used to:
"Additional fixture offsets, G54.1 Pxx, can also be set using G10.
"Setting of these offsets is the same, except it is done using L20."
so I conclude that it cannot be used to zero the DROs.

wbr Kusti




6
Thanks for the example and Roger's guide.

I guess I need to experiment a bit to see what really happens, looks like this is somewhat uncharted even if Roger has done a good write up.

wbr Kusti

7
Thanks Tweakie!

This is all new territory for me.

I downloaded the spread sheet and google a bit about OEM DROs but the penny did not drop,
can you give a concrete example please?

Say may abs machine position X=100, supposing my current work offset set is 1 (G54),
the if I press ZERO this will set X of work offset 1 to 100 and the X DRO reads now 0, correct?

So exactly how would I do this in G-code?

wbr Kusti



8
I would like to set DROs to zero (or any other value) from G-code without touching the G54/G92 offsets.

I've not tried this but from reading the LinuxCNC documentation it seems to me that this can be done with:

G10 L20 P1 X0 Y0 Z0

But reading the Mach documentation this does not seem to be supported.

Is there a G-code in Mach dialect that allows me to do that?

Also I note that Fanuc and other seem to interpret L20 differently from LinuxCNC so
I'm awarding extra points for answers that are 'platform' indendent ;)

cheers Kusti



9
G-Code, CAD, and CAM discussions / Re: G-code oddities..
« on: November 02, 2010, 02:13:33 AM »
Yeah! Thanks.

10
G-Code, CAD, and CAM discussions / Re: G-code oddities..
« on: November 01, 2010, 05:26:04 AM »
Here is what your code looks like on a running machine. Notice the change of code required to "make" it run. The original code as you posted it is an error with the 3rd line. Also note that the G42 has NOT been cancelled.

Thanks TP for your trouble, yes you are right that there was an error in line 3, but it was deliberate: I was trying to see what happens. Did you get an error message on line 3 or what...?


br Kusti

Pages: 1 2 »