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

Bed temp not set by slicer w/ Klipper g-code flavor #485

Closed
OldCurmudgeon3DP opened this issue Sep 19, 2020 · 1 comment
Closed

Bed temp not set by slicer w/ Klipper g-code flavor #485

OldCurmudgeon3DP opened this issue Sep 19, 2020 · 1 comment
Labels
enhancement fix is live in the last release Please download /build the last release and try to reproduce.

Comments

@OldCurmudgeon3DP
Copy link

Version

2.2.53

Operating system type + version

Win 7

3D printer brand / version + firmware version (if known)

Ender 3 modded
Klipper, updated this week

Behavior

Bed temp g-code (M140 or M190) is not being injected into the file when Klipper g-code flavor is selected in Printer tab. 50C is set in the Filament tab. Is this a feature, a bug, or setting I missed in a tab?

@supermerill
Copy link
Owner

supermerill commented Sep 19, 2020

Put it on the start-gcode.
It's because klipper use of macros and so it won't add it by itself to avoid conflicts. Most klipper user prefer to write PRINT_START EXTRUDER_TEMP=[first_layer_temperature] BED_TEMP=[first_leyer_bed_temperature] and let their klipper macro handle it the way it's best for the printer. that way, if yo want to modify your start procedure, you only need to modify it on one point : klipper.

Now that i think of it, I can return to legacy behavior if there is nothing inside 'start gcode'.

@supermerill supermerill added enhancement not convinced yet fixed for the next version That means that you should be able to test it in the latest nightly build and removed not convinced yet labels Sep 19, 2020
@supermerill supermerill added fix is live in the last release Please download /build the last release and try to reproduce. and removed fixed for the next version That means that you should be able to test it in the latest nightly build labels Oct 5, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement fix is live in the last release Please download /build the last release and try to reproduce.
Projects
None yet
Development

No branches or pull requests

2 participants