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

[ENHANCEMENT]Allow Z heights to be stored as presets for different filament types #2899

Closed
DylanBarber opened this issue Nov 20, 2020 · 6 comments

Comments

@DylanBarber
Copy link

Please, before you create a new feature request, please make sure you searched in open and closed issues and couldn't find anything that matches.

Enter what type of printer or upgrade the enhancement applies to.
Printer type - [e.g. MK3S, MK3], may also apply to other printers

**Is your enhancement related to a problem? -No

Describe the solution you'd like

PETG requires the nozzle to be further away from the bed than with PLA. Because of this I'm always adjusting my Z height (distance from the bed) when swapping between the two types of filament.

My enhancement suggestion is adding something in the menu, prior to printing, that allows you to save the Z height presets for multiple filaments and apply them BEFORE starting the print.

Suggested flow:

Menu -> Z Heights -> Menu displaying the following:

PETG: -0.580
PLA: -0.565
ABS: -0.575
ASA: -0.580

Then allow the user to select their Z height preset

Currently I'm just storing these values in a .txt file on my computer and then rushing to change it once my print starts but it would be so much more convenient if it existed in the firmware.

Thanks!

@DylanBarber DylanBarber changed the title [ENHANCEMENT]<Enter comprehensive title> [ENHANCEMENT]Allow Z heights to be stored as presets for filament types Nov 20, 2020
@DylanBarber DylanBarber changed the title [ENHANCEMENT]Allow Z heights to be stored as presets for filament types [ENHANCEMENT]Allow Z heights to be stored as presets for different filament types Nov 20, 2020
@vintagepc
Copy link
Contributor

You could do this with different sheet profiles for the same sheet - have you tried that feature?

@StarWitch
Copy link

Would there be some way of detecting filament type based on GCode and then loading the "filament-type height offset" and applying it to the base Z adjustment? i.e:

Base Z Adjustment: -0.900
PLA: +/-0.00
PETG: +0.15
ASA: +0.10

etc, etc.

@vintagepc
Copy link
Contributor

I don't think they want to support that as it's a somewhat "risky" feature in terms of the printer damaging itself. It also potentially makes the g-code completely non-portable to other machines.

#2201 might be of interest to you though.

@StarWitch
Copy link

StarWitch commented Nov 22, 2020

Oh, I didn't mean baking the offsets into the GCode itself, but rather just the filament type.

When you generate GCode with something like the MMU2S, you can see filament_type in the GCode as a comment listing the five filament types for each nozzle. One option would have the printer detect that filament_type for just a single value, and then apply the offset automatically based on settings on the printer itself. If a printer doesn't acknowledge the filament_type comment or if it's a filament type the printer doesn't recognize or have a preset for, then it just uses its own preset Z-height, no different than before.

I do like your PR #2201 though! Having it be a setting in PrusaSlicer or something like that would be just as good, I think, although it does run the risk of being non-portable if some other printer uses M850 for its own purpose, but the risk of that collision is relatively low.

@github-actions
Copy link

This issue has been flagged as stale because it has been open for 60 days with no activity. The issue will be closed in 7 days unless someone removes the "stale" label or adds a comment.

Copy link

github-actions bot commented Nov 2, 2023

This issue has been closed due to lack of recent activity.

@github-actions github-actions bot closed this as not planned Won't fix, can't repro, duplicate, stale Nov 2, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants