# All temeratures are 0 as soon as first layer starts / Slicer-Start Macro-Klipper interdependency

**URL:** <https://klipper.discourse.group/t/all-temeratures-are-0-as-soon-as-first-layer-starts-slicer-start-macro-klipper-interdependency/16013>\
**Category:** General Discussion\
**Created:** [April 25, 2024, 3:39am UTC](https://klipper.discourse.group/t/all-temeratures-are-0-as-soon-as-first-layer-starts-slicer-start-macro-klipper-interdependency/16013 "2024-04-25T03:39:37Z")\
**Posts on this page:** 8\
**Page:** 1

<div class="post-metadata">

**Author:** ![remarkable\_sir](https://avatars.discourse-cdn.com/v4/letter/r/e8c25b/32.png) [@remarkable\_sir](https://klipper.discourse.group/u/remarkable_sir)\
**Post date:** [April 25, 2024, 3:39am UTC](https://klipper.discourse.group/t/all-temeratures-are-0-as-soon-as-first-layer-starts-slicer-start-macro-klipper-interdependency/16013/1 "2024-04-25T03:39:37Z")

</div>

### Basic Information:

Printer Model: Qidi xmax 3 vanlla klipper 0.12  
 MCU / Printerboard: MKSPI  
 Host / SBC  
 klippy.log

hey!

I use orcaslicer and a vanilla klipper printer and have not tuned in everything yet.  
i.e. I have the problem that all temps are reduced to zero after initial warm up and print start.

I believe it has something to do with the start\_print macro but wonder about it.

Can you please let me know a place where to go?  
Im not sure if this is the right place here since I suspect rather a configuration issue in conjuction with the use of Orca than a Klipper problem.

Happy to hear your feedback about my macrosin case you find obvious flaws. Thank you!

[klippy.log](https://klipper.discourse.group/uploads/short-url/xlmtzYhEysDhVsUHbpzZ3eBtGbq.log) (112.1 KB)  
[macros.cfg](https://klipper.discourse.group/uploads/short-url/rK2dEC5mA6YLJjdRX5b5kGEOP0g.cfg) (9.8 KB)

---

<div class="post-metadata">

**Author:** ![EddyMI3D](https://yyz2.discourse-cdn.com/free1/user_avatar/klipper.discourse.group/eddymi3d/32/1981_2.png) [@EddyMI3D](https://klipper.discourse.group/u/EddyMI3D)\
**Post date:** [April 25, 2024, 5:11am UTC](https://klipper.discourse.group/t/all-temeratures-are-0-as-soon-as-first-layer-starts-slicer-start-macro-klipper-interdependency/16013/2 "2024-04-25T05:11:58Z")

</div>

> [@remarkable\_sir](#):
>
> a vanilla klipper

```auto
Git version: 'v0.12.0-171-g2f6e94c9-dirty'

```

Not quite vanilla.

The klippy.log is quite short (except the bedmesh coordinate: almost 1000 lines).  
There is no heating up and/or cancelling to find.

Please start a print again, when the issue occurs, do a M112 and attach the new klippy.log to your next post. Also the Gcode file that you want to print and/or the start print script from OrcaSlicer.

---

<div class="post-metadata">

**Author:** ![remarkable\_sir](https://avatars.discourse-cdn.com/v4/letter/r/e8c25b/32.png) [@remarkable\_sir](https://klipper.discourse.group/u/remarkable_sir)\
**Post date:** [April 25, 2024, 6:49am UTC](https://klipper.discourse.group/t/all-temeratures-are-0-as-soon-as-first-layer-starts-slicer-start-macro-klipper-interdependency/16013/3 "2024-04-25T06:49:06Z")

</div>

yes sure, will do.  
It is short because I set up the system fresh just before and this was the first print.

here is the gcode file:

[adapterplate\_2024\_PETG\_54m30s.gcode](https://klipper.discourse.group/uploads/short-url/4sciIlOMafYH5Rg907OXplSkDZN.gcode) (973.2 KB)

This is the start Gcode in the slicer:

> START\_PRINT EXTRUDER\_TEMP=[first\_layer\_temperature] BED\_TEMP=[first\_layer\_bed\_temperature]  
> CHAMBER=[chamber\_temperature]
> 
> M104 S0 ; Stops OrcaSlicer from sending temp waits separately  
> M140 S0

Here I reproduced the error and this time executed M112 after “Temp extruder too low” notification popped up.

[klippy (1).log](https://klipper.discourse.group/uploads/short-url/7yGYVdVTRcCHkHLkQLwUSxnEvEm.log) (1.4 MB)

---

<div class="post-metadata">

**Author:** ![EddyMI3D](https://yyz2.discourse-cdn.com/free1/user_avatar/klipper.discourse.group/eddymi3d/32/1981_2.png) [@EddyMI3D](https://klipper.discourse.group/u/EddyMI3D)\
**Post date:** [April 25, 2024, 7:10am UTC](https://klipper.discourse.group/t/all-temeratures-are-0-as-soon-as-first-layer-starts-slicer-start-macro-klipper-interdependency/16013/4 "2024-04-25T07:10:30Z")

</div>

```auto
START_PRINT EXTRUDER_TEMP=[first_layer_temperature] BED_TEMP=[first_layer_bed_temperature]
CHAMBER=[chamber_temperature]

M104 S0 ; Stops OrcaSlicer from sending temp waits separately # <--------
M140 S0 # <--------

```

You turn them off yourself.

* * *

This occurs:

```auto
Unknown command:"CHAMBER=0"

```

This in the gcode file

```auto
START_PRINT EXTRUDER_TEMP=250 BED_TEMP=80
CHAMBER=0

```

should be one line

```auto
START_PRINT EXTRUDER_TEMP=250 BED_TEMP=80 CHAMBER=0

```

So in the slicer

```auto
START_PRINT EXTRUDER_TEMP=[first_layer_temperature] BED_TEMP=[first_layer_bed_temperature] CHAMBER=[chamber_temperature]

```

---

<div class="post-metadata">

**Author:** ![remarkable\_sir](https://avatars.discourse-cdn.com/v4/letter/r/e8c25b/32.png) [@remarkable\_sir](https://klipper.discourse.group/u/remarkable_sir)\
**Post date:** [April 25, 2024, 12:10pm UTC](https://klipper.discourse.group/t/all-temeratures-are-0-as-soon-as-first-layer-starts-slicer-start-macro-klipper-interdependency/16013/5 "2024-04-25T12:10:37Z")

</div>

> [@EddyMI3D](#):
>
> ```auto
> M104 S0 ; Stops OrcaSlicer from sending temp waits separately # <--------
> M140 S0       
> 
> ```

Nice 👍  
Commented this out and removed excess line breaks. Works!!

Regarding chamber unknown command. I still had chamber\_heater in the configuration. So I had to rename this one and this error is gone as well.

I copied the slicer start G codes from somewhere. I think Orca is having this as a recommendation. Didn’t give it a lot of thought but obviously it was completely wrong.

---

<div class="post-metadata">

**Author:** ![EddyMI3D](https://yyz2.discourse-cdn.com/free1/user_avatar/klipper.discourse.group/eddymi3d/32/1981_2.png) [@EddyMI3D](https://klipper.discourse.group/u/EddyMI3D)\
**Post date:** [April 25, 2024, 12:31pm UTC](https://klipper.discourse.group/t/all-temeratures-are-0-as-soon-as-first-layer-starts-slicer-start-macro-klipper-interdependency/16013/6 "2024-04-25T12:31:57Z")

</div>

> [@remarkable\_sir](#):
>
> I copied the slicer start G codes from somewhere.

That’s the problem with copy random scrips.  
Check what they do before using them.

---

<div class="post-metadata">

**Author:** ![remarkable\_sir](https://avatars.discourse-cdn.com/v4/letter/r/e8c25b/32.png) [@remarkable\_sir](https://klipper.discourse.group/u/remarkable_sir)\
**Post date:** [April 25, 2024, 1:45pm UTC](https://klipper.discourse.group/t/all-temeratures-are-0-as-soon-as-first-layer-starts-slicer-start-macro-klipper-interdependency/16013/7 "2024-04-25T13:45:45Z")

</div>

Well it’s the oem recommendation for this printer type in conjunction with Orcaslicer. I think that’s why I didn’t second guess the code. Really strange. Will double check since it really doesn’t make sense now when I look at it. The scary part is that I could have sworn that it worked quite good last week with the same slicer settings 🤷‍♂️

Thanks again, really great feeling to have a good working machine.

PS: I have one last Linux issue and in depth questions regarding lsmod and kernel modules.  
Where is a good place to go for these Linux-3D print-armbian questions?

---

<div class="post-metadata">

**Author:** ![system](https://global.discourse-cdn.com/free1/uploads/klipper/original/1X/64419bf2aac6639e6ef5cef200dcd456b0a01ac3.png) [@system](https://klipper.discourse.group/u/system)\
**Post date:** [May 25, 2024, 11:46pm UTC](https://klipper.discourse.group/t/all-temeratures-are-0-as-soon-as-first-layer-starts-slicer-start-macro-klipper-interdependency/16013/8 "2024-05-25T23:46:01Z")

</div>

This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.