Move out of range after Print end

[ornate owl]

Sometimes I encounter the error move out of range. It is at the end of a print and because the machine dont want to go to y 350.012 which I can understand 😉 because its maximum is 350mm. What I don't understand is why the machine gets the instructions to go to 350.012. ( and also X175.009 ?)It is limited in the slicer. And because it is such a small amount I'm curious where it comes from. I already changed the end position to 349 but sometimes i still get the error. Also the move happens after the G90 command is issued in the Print_end macro i think. Someone any ideas?

[gcode_macro PRINT_END]
gcode:
SAVE_GCODE_STATE NAME=STATE_PRINT_END

M400                           ; wait for buffer to clear
G92 E0                         ; zero the extruder
G1 E-10.0 F3600                ; retract filament

G91                            ; relative positioning
G0 Z1.00 X20.0 Y20.0 F20000    ; move nozzle to remove stringing
TURN_OFF_HEATERS
M107                           ; turn off fan
G1 Z2 F3000                    ; move nozzle up 2mm
G90                            ; absolute positioning
G0  X175 Y349 F3600            ; park nozzle at rear
BED_MESH_CLEAR
SET_GCODE_OFFSET Z=0.0
RESTORE_GCODE_STATE NAME=STATE_PRINT_END MOVE=0

[abstract mulch]

@ornate owl When posting configs or logs, please surround with code fences (```) so that Discord formats them correctly. Example:
```ini
[mcu]
serial: /dev/serial/by-id/usb-klipper-12345-if00
```

[mcu]
serial: /dev/serial/by-id/usb-klipper-12345-if00

[wise vine]

so, as per the comment, G91 puts the coordinate system into relative mode and then it's attempting to move the toolhead 20 mm in x and y, and 1 mm in z, but the z movement is not relevant here

depending on where your toolhead is at the end of the print, it may try and move out of bounds

for example,, if your toolhead ends up at 330.012 in the x axis and it tried to move 20mm, that'd result in an invalid location of 350.012

[ornate owl]

Yeah that's true, but I don't think that is where it happened. It happens at the move X175 X350 (349)

Also the move X175 is incorrect by a small amount

Which doesn't cause the error but still weird

[wise vine]

there's nothing after the G90 that would cause a movement out of range

[ornate owl]

Yeah thats why I'm confused 😉

If it was the G91 X20 Y20 move it would be very coincidental that the last position was X155.009 and Y330.012 right? 😉

But also true that the G91 X20 Y20 move is probably not the best move at the end of a print in case it ends up close to the out of range area