-
Please try firmware 1.21RC5. I believe that workspace coordinates are working correctly in it (including G53 being non-model), with the caveat that this command:
G53 G1 Xnn Ynn …
will work correctly; whereas this:
G1 G53 Xnn Ynn
will not.
-
Please try firmware 1.21RC5. I believe that workspace coordinates are working correctly in it (including G53 being non-model), with the caveat that this command:
G53 G1 Xnn Ynn …
will work correctly; whereas this:
G1 G53 Xnn Ynn
will not.
I will give it a try later today.
Interesting case you have with "G53 G1 coords" vs. "G1 G53 coords". I can sort of see the technical parsing assumptions behind both being valid… at the same time, I've never seen a CAM generated line, or a human generated line of the "G1 G53 ..." variety. Personally, I'd be OK with not covering that case.
-
Hmmmm…. The following would also be valid:
[[language]] G54 G1 Xnnn Ynnn ;Moves to currently active G54 Work Coordinates G53 Xnnn Ynnn ;Moves to machine coordinates Xnnn Ynnn ;Moves to currently active G54 Work Coordinates. G55 Xnnn Ynnn ;Moves to currently active G55 Work Coordinates.And so forth. G1 stays active until another Group1 command is executed.
And, I HAVE seen CAM generated code that looks something like that. Therefore, I take back what I said… eventually, the modalities would need to be correct.
-
New thread that re-summarizes a ton of things about CNC coordinates here:
