Doubts about temperatures and slicers

General Discussion
1

Basic Information:

Printer Model: Vcore 31
MCU / Printerboard: Octopus Max
Host / SBC Rpi4
klippy.log

klippy.log (10).txt (51.8 KB)

Fill out above information and in all cases attach your klippy.log file (use zip to compress it, if too big). Pasting your printer.cfg is not needed
Be sure to check our “Knowledge Base” Category first. Most relevant items, e.g. error messages, are covered there

Describe your issue:

Hi,

In my workflow, when I turn on the printer, I have it preheat via the web interface to temperatures close to the printing temperature.

Each print job is configured to a different temperature for the first layer and the rest of the print using the slicer; in my case, I usually use ORCA.

Well, the temperature remains at the one I’ve set to preheat the printer. It doesn’t change even if a different temperature is selected in the slicer, at least not when I use Klipper.

I suppose this is a problem with the slicer itself, rather than Klipper.

Is there any way to force this to happen? When I start printing, I want the printer to reach the temperature specified in the slicer, instead of using the one I’ve preselected.

Another issue, which I suspect is related, is that I used to use Cura, and the startup routine was different. The printer was preheated, and I gave it the command to print a gcode, which had different temperatures than the preheating temperature I had indicated, because the printing did NOT start until the temperature was the one I had configured in CURA.

…

2

Please post the start gcode that is in your slicer.

Have you coped the start code from CURA to OrcaSlicer 1:1?
Keep in mind, that these slicers have different tokens for the gcode start setup.

3

I use macros, so the startup G-code is the same regardless of the slicer I use…

My macro that runs the slicer is:

“EMPEZAR_IMPRESION”

and it contains this:

 [gcode_macro EMPEZAR_IMPRESION]
gcode:
    G90 ;Coordenadas absolutas
    G1 Z20.0 F6000 ;Move the platform down 15mm    ; Prime the extruder
    G92 E0
    
    BED_MESH_CLEAR
    BED_MESH_CALIBRATE ADAPTIVE=1
    BED_MESH_PROFILE SAVE=<MallaAnterior>
    M220 S20
    G28 Z
4

In that macro, no temperature values are passed over.

You can do the temperature settings in OrcaSlicer.
With my settings the start gcode in OrcaSlicer is this:

M82
M355 S1                                     ; OP
M106 P0 S0
M106 P1 S0
M140 S[bed_temperature]
M109 S([first_layer_temperature_0] * 0.75) T0
M190 S[bed_temperature]
M109 S[first_layer_temperature_0] T0
G90
BED_MESH_CLEAR
G28        
...
1 Like
5

I’ve modified the macro to start printing; I’ve included those two lines… I’ll check it on the next print job…

 [gcode_macro EMPEZAR_IMPRESION]
gcode:
    M190 S[bed_temperature]
    M109 S[first_layer_temperature_0] T0
    G90 ;Coordenadas absolutas
    G1 Z20.0 F6000 ;Move the platform down 15mm    ; Prime the extruder
    G92 E0
    
    BED_MESH_CLEAR
    BED_MESH_CALIBRATE ADAPTIVE=1
    BED_MESH_PROFILE SAVE=<MallaAnterior>
    M220 S20
    G28 Z

What I find strange is the difference in temperature management between ORCA and CURA (and I think Prusa Slic3r, I’m not sure). The other slicers seem to be doing things more reasonably…

6

No, these belong to the OrcaSlicer start gcode.

grafik
grafik1063×831 91.6 KB