Work Coordinate system and pause

  • I'm curious how the G1 R1 works with pause, resume, and multiple work offsets. First a little background info. I am using a slicer for work that will only locate the part at the origin, but this is undesirable so I want to use work coordinate systems to offset the origin. I have to be able to switch back to machine coordinates when pausing and doing tool changes. I have been able to get this to work by using G10 L2 P2 X Y Z and then inserting G54 and G55 in my macros. For example, before the move to the tool change or pause position I put a G54, and on tpost or resume I put a G55. Is the G55 necessary? Will the G1 R1 return to the correct work coordinate system?
    I'm not really sure I need to use more than one work coordinate system, but I am curious about the capabilities of this.

  • administrators

    This is the situation in RRF 2.03 and 2.04RC1. When system macro files such as pause.g are run, workplace coordinates are ignored, so all GCode commands in pause.g are executed as if no workplace coordinates are in effect. Tool offsets will still be applied. The resume coordinate is saved in absolute coordinates, so G1 R1 X0 Y0 Z0 will return to the correct location - although that is executed automatically at the end of executing resume.g anyway.

  • As always thanks for the quick reply. This is what I was hoping for, but just to double check if I were to add the following to my start script:

    G10 L2 P2 X50 Y50 Z0 ; set offsets for coordinate system G55, sets G55 origin at X50Y50Z0
    G55 ; Use coordinate system G55

    I should expect the toolpaths to shift 50 in X and 50 in Y, but system macros will go to the same physical locations as if the G10 and G55 weren't present. So the G54 and G55 I added to system macros can be removed.

    Does G28 also behave as expected? Using the offsets above, If I home in G55, then command G1 X0Y0, then command G54 the coordinates should display X50 Y50 and the physical location is the same as commanding G54 G28 G1 X50 Y50?

  • I was able to confirm this works as expected.

Log in to reply