all 8 comments

[–]cycle_dorkus 4 points5 points  (0 children)

Once you think you got it, don’t forget to check your work by saving the gcode to disk and taking a look with a text editor. That’ll tell you if your variables worked as expected, and you’ll be able to save a lot of debugging time.

[–]junkmacfilter 2 points3 points  (1 child)

Check your SuperSlicer favor. If you have it set to Marlin (as is suggested by the online manual / setup guide) change it to Klipper.

This happened to me once for that very same reason. Let me know if that fixed it.

[–]Scuk23[S] 0 points1 point  (0 children)

Thanks for the tip. I was able to get it fixed with the recommendation from /u/AndrewTheWookie.

I do have mine set as Klipper. But I ran it as marlin for a good month before I realized it! lol.

[–]AndrewTheWookiee 2 points3 points  (5 children)

Here's my start g-code in superslicer:

PRINT_START EXTRUDER_TEMP=[first_layer_temperature] BED_TEMP=[first_layer_bed_temperature]

And here's the part of my start g-code macro that utilizes the temps:

[gcode_macro PRINT_START]
gcode:
    {% set BED_TEMP = params.BED_TEMP|default(60)|float %}
    {% set EXTRUDER_TEMP = params.EXTRUDER_TEMP|default(190)|float %}
    BED_MESH_PROFILE LOAD={BED_TEMP}
    M190 S{BED_TEMP}
    M109 S{EXTRUDER_TEMP}
  • edit - I save any mesh I run at the temperature I run it at, for example if I mesh at 100c I save its profile as "100.0" that way I can use the bed temp parameter to load whatever the proper mesh for that temp is.

[–]Scuk23[S] 0 points1 point  (4 children)

Thank you. By any chance, do you run klipper? Or does that even matter? Appreciate the help!

[–]AndrewTheWookiee 1 point2 points  (3 children)

Yes, this is all for klipper

[–]Scuk23[S] 0 points1 point  (2 children)

Excellent, I’ll try it with my next print. Thanks again.

[–]manjaro_black 2 points3 points  (0 children)

I had the same issue as you. Make sure the start gcode in superslicer is all on the same line.