Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add current job XY min max values to OM #941

Open
droftarts opened this issue Jan 10, 2024 · 0 comments
Open

Add current job XY min max values to OM #941

droftarts opened this issue Jan 10, 2024 · 0 comments
Assignees
Labels
enhancement Additional functionality, performance or other feature request
Milestone

Comments

@droftarts
Copy link

Is your feature request related to a problem? Please describe.

Add current job XY min max values to OM. This would allow for easier definition of selective mesh probing, and for drawing boundary boxes for laser cutters. Could also be used as a check to see if the job fits on the bed.

Describe the solution you propose.

Lightburn has added XY min max to the comments in generated gcode files, to allow a bounding box to be drawn.

Lightburn example:
from jay_s_uk on forum: https://forum.duet3d.com/topic/34581/frame-job-boundaries/6

; LightBurn 1.4.04
; GRBL device profile, absolute coords
; Bounds: X5 Y5 to X105 Y155

Slicers such as Prusaslicer, Ideamaker have variables for at least the first layer, but not automatically added to comments in generated Gcode files. Workarounds for other slicers, eg Cura, exist, but if added to 'start G-code', the format of the comment needs to be defined. Other slicers have not been checked.

Prusaslicer example:
Prusaslicer 'placeholders' need to be added to custom 'start G-code', format needs to be defined. eg:

; Bounds: X{first_layer_print_min[0]} Y{first_layer_print_min[1]} to X{first_layer_print_max[0]} Y{first_layer_print_max[1]}

produces

; Bounds: X-18.1724 Y-40.2153 to X33.8542 Y18.1724

A script exists for selective bed mesh probing from Prusaslicer, Cura and Ideamaker, using the variables to call a macro, see https://forum.duet3d.com/topic/29576/only-probe-where-the-part-will-be-printed/47

If these can be extracted and added to the OM in variables called something like job.file.firstLayerMin{X,Y} and job.file.firstLayerMax{X,Y}

Describe alternatives you've considered

A script exists for selective bed mesh probing from Prusaslicer, Cura and Ideamaker, using the variables to call a macro, see https://forum.duet3d.com/topic/29576/only-probe-where-the-part-will-be-printed/47

A Gcode post-processor or plugin could be written that parses the whole Gcode file to find min and max X and Y.

Provide any additional context or information.

No response

@droftarts droftarts added the enhancement Additional functionality, performance or other feature request label Jan 10, 2024
@droftarts droftarts added this to the 3.5.0 milestone Jan 10, 2024
@T3P3 T3P3 modified the milestones: 3.5.0, 3.6.0 Jan 10, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement Additional functionality, performance or other feature request
Projects
None yet
Development

No branches or pull requests

3 participants