G10 L2

More
06 Jul 2013 12:32 - 06 Jul 2013 12:34 #36355 by Todd Zuercher
G10 L2 was created by Todd Zuercher
Would the line:
G10 L2 P1X1
be functionally equivalent to
#5221=[1]
Last edit: 06 Jul 2013 12:34 by Todd Zuercher.

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

More
06 Jul 2013 23:53 #36367 by ArcEye
Replied by ArcEye on topic G10 L2
Hi

I think the answer to that is not of itself

See attached test where origin of X was set to 3 and then #5221 set to 0 and a print of #5221 confirmed that value to the terminal, but the offset remained when the program was started

If you messed about with G92, that might have been different




regards
Attachments:

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

More
07 Jul 2013 03:56 #36369 by BigJohnT
Replied by BigJohnT on topic G10 L2

Would the line:
G10 L2 P1X1
be functionally equivalent to
#5221=[1]


No, for many reasons that I can't fully explain.

Why would you want to do that?

JT

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

More
08 Jul 2013 09:16 #36388 by Todd Zuercher
Replied by Todd Zuercher on topic G10 L2
my reason is that I would like to set up a Halui command to change the offsets of more than one work coordinate system in one fell swoop. As far as I can tell I can only effect one set of work coordinates in a single line with G10 but using #xxxxx=y, I was hoping I could string together as many as I need on one line. (To for example change the X offset of G54 and G55 in a single command.)

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

More
08 Jul 2013 09:43 #36389 by Todd Zuercher
Replied by Todd Zuercher on topic G10 L2
a quick bit of experimentation showed me that if I issued #5221=[1] then changed from g54 to another (g55) then changed back to g54 it seems to work. But only commanding G54 when already using the g54 coordinates doesn't effect the change. I also found that #5221=[1] G10L2P1 does seem to work, but might not help me. since I can not guarantee or predict exactly what coordinate system might be in effect when my Halui command is used.

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

More
08 Jul 2013 14:30 #36392 by ArcEye
Replied by ArcEye on topic G10 L2

my reason is that I would like to set up a Halui command to change the offsets of more than one work coordinate system in one fell swoop. As far as I can tell I can only effect one set of work coordinates in a single line with G10 but using #xxxxx=y, I was hoping I could string together as many as I need on one line. (To for example change the X offset of G54 and G55 in a single command.)



How about writing a sub which contains all the G10 L2 lines that you need and call that sub from halui?

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

More
08 Jul 2013 18:12 #36394 by BigJohnT
Replied by BigJohnT on topic G10 L2

a quick bit of experimentation showed me that if I issued #5221=[1] then changed from g54 to another (g55) then changed back to g54 it seems to work. But only commanding G54 when already using the g54 coordinates doesn't effect the change. I also found that #5221=[1] G10L2P1 does seem to work, but might not help me. since I can not guarantee or predict exactly what coordinate system might be in effect when my Halui command is used.


The developer I asked warned me that if read only had been available when the numbered parameters for coordinate system were created they would have been read only. He also warned about a few other things that I forget. You could read the #linuxcnc-devel logs it you're interested in the exact conversation.

I highly suggest you use G code to change the offsets and as ArcEye suggests use a sub.

JT

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

Time to create page: 0.147 seconds
Powered by Kunena Forum