Slicing allows gcode to exceed X (maybe Y aslso) max limit

[Fonzi03]

Is there an existing issue for this problem?

• I have searched the existing issues

OrcaSlicer Version

Exceeding max print area with no warning

Operating System (OS)

Windows

OS Version

Win 11 24H2

Additional system information

This happened in 2.1.1 then I upgrade to 2.2.0 same issue. A print is capable of exceeding the max print volume with no warnings. In this instance my max X is 247 but the sliced gcode is trying to send it to 248.7 for some reason. Normally I see an error when I exceed the printable area, not sure if this has anything to do with height above the print area or not but its super frustrating as I have no clear way to tell what the max X/Y is in the gcode without sifting through the whole thing.

Printer

Custom

How to reproduce

My bed settings are set to the following:
Size: 247,245
Origin: -16,-13

My x and y end stops are further than the end of my bed but thats obviously not printable area.

My file is attached.

[stepper_y] step_pin: PB10 dir_pin: !PB2 enable_pin: !PB11 microsteps: 64 rotation_distance: 40 endstop_pin: ^PC1 position_endstop: 0 position_min: 0 position_max: 245 homing_speed: 50

[stepper_x] step_pin: PB13 dir_pin: !PB12 enable_pin: !PB14 microsteps: 64 rotation_distance: 40 endstop_pin: ^PC0 position_endstop: 0 position_min: 0 position_max: 247 homing_speed: 50

Actual results

Print fails due to exceeding the limits in my printer.config

Expected results

I should get a warning if any part of gcode exceeds the exact number typed into the bed settings, ensure there are no rounding errors and such as even going over by .001 would cause a failure.

Project file & Debug log uploads

9in Disk Sander vacuum attachment.zip

Checklist of files to include

• Log file
• Project file

Anything else?

No response