Incremental Offset from G54

More
22 Sep 2015 19:29 #62852 by nooob
Hi guys,

is it possible to make an incremental Offset from G54?

Lets say i want to move G54 2mm in Z+ is there any code for that?

in other controls for example Heidenhain you say
CYCLE DEF 7.0 DATUM SHIFT 

CYCLE DEF 7.1 Z+1

u can read about it here on Page 235: >>CLICK ME<<

greetings nooob

Please Log in or Create an account to join the conversation.

More
22 Sep 2015 22:38 #62859 by Todd Zuercher
Sort of. There isn't a specific incremental shift command. But you can achieve the same effect with the G10L2 command combined with the coordinated system parameter number for the axis you want to shift. such as this
G10 L2 P1 Z[#5223 + 2.0]

This would shift your Z G54 2mm (if you were in G21 mode).

I am not sure if this would work but it might achieve the same effect
#5223=[#5223 + 2.0]

but I know the first example works see here for the parameter numbers for other axis and coordinate systems
linuxcnc.org/docs/2.6/html/gcode/overvie...umbered_parameters_a

Please Log in or Create an account to join the conversation.

More
22 Sep 2015 22:55 - 22 Sep 2015 22:59 #62862 by Todd Zuercher
I quick tested it and the second example and while it does change the value of the stored parameter, it doesn't update the DRO and my not work in a program by itself. but if it is followed with G10 L2 P1. The DRO updates to the new value stored int the parameters.

so it seems that
#5221=[#5221+1]
G10 L2 P1
is equivalent to
G10 L2 P1 X[#5221 + 1]
Last edit: 22 Sep 2015 22:59 by Todd Zuercher.

Please Log in or Create an account to join the conversation.

More
22 Sep 2015 23:18 #62865 by andypugh

I quick tested it and the second example and while it does change the value of the stored parameter, it doesn't update the DRO and my not work in a program by itself. but if it is followed with G10 L2 P1. The DRO updates to the new value stored int the parameters.


Does it actually update the axis offsets, though? I wouldn't necessarily expect it to. I think that the numbered parameters are one-way mirrors of the internal offset numbers, but they may also be what Axis is using to calculate DRO values. If that is the case then there might be a discrepancy between the DRO and actual machine position.

I think that the first option (computed G10) is the most reliable solution.
The following user(s) said Thank You: nooob

Please Log in or Create an account to join the conversation.

More
23 Sep 2015 00:13 #62866 by nooob
Replied by nooob on topic Incremental Offset from G54
Thanks for the fast answers

i will try it tomorrow on my machine.

Im wondering that no one is missing this feature expect me until now, are u guys using a different method?

i'll guess

#5221 is X-Axis
#5222 is Y-Axis
#5223 is Z-Axis

right?

Please Log in or Create an account to join the conversation.

More
23 Sep 2015 01:44 #62869 by Todd Zuercher
Yes that is right.

I actually have a series of pyvcp buttons set up (laid out like a jog keypad) for incrementally jogging the G54 offsets on one machine.

+Z+Y+W
-X ? +X
-Z -Y -W

these are linked a bunch of halui commands of G10L2P1[#522n +?]

I'm guessing most people just use the tool touch off widget in axis.

It might be a worthwhile endeavor to try to use remap to make the G- code you need (perhaps a G10L2.1 for incremental adjustments)
The following user(s) said Thank You: nooob

Please Log in or Create an account to join the conversation.

More
23 Sep 2015 14:23 #62878 by nooob
Replied by nooob on topic Incremental Offset from G54
i tested it, it works great!

thank u Todd and andy.

I think i will try to make me an pyvcp for this :)

Greetings from Germany

Please Log in or Create an account to join the conversation.

Time to create page: 0.189 seconds
Powered by Kunena Forum