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

Using start g_code #10018

Closed
1 of 2 tasks
mumrikmamrik opened this issue Mar 11, 2023 · 2 comments
Closed
1 of 2 tasks

Using start g_code #10018

mumrikmamrik opened this issue Mar 11, 2023 · 2 comments

Comments

@mumrikmamrik
Copy link

Description of the bug

I'm using prusaslicer with Klipper and start g-code is written in Klipper and in prusaslicer start g-code is only
"START_PRINT EXTRUDER_TEMP=275 BED_TEMP=105".
Prusaslicer (i suppose) parce my start g-code, found that i'm not heating extruder and bed and decide to do this itself without any exception.

btw, add klipper config.

Project file & How to reproduce

add START_PRINT EXTRUDER_TEMP=275 BED_TEMP=105 to any start_code and delete any other start preheat code

Checklist of files included above

  • Project file
  • Screenshot

Version of PrusaSlicer

2.6.0-alpha5

Operating system

macOS 12.6

Printer model

ender3, klipper

@Gunner087
Copy link

@mumrikmamrik this can be worked around for now by adding "M190 S0" and "M109 S0" commands to the very beginning of your start gcode. This prevents PrusaSlicer from automatically adding the temperature commands after the start gcode.
Screenshot 2023-03-18 at 2 31 49 PM

@lukasmatena
Copy link
Collaborator

Setting temperatures automatically is optional since 2.6.0-alpha6. Closing.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants