Duet3D Logo Duet3D
    • Tags
    • Documentation
    • Order
    • Register
    • Login

    Error: M141: No chamber heater has been configured for slot 0

    Scheduled Pinned Locked Moved
    General Discussion
    3
    10
    657
    Loading More Posts
    • Oldest to Newest
    • Newest to Oldest
    • Most Votes
    Reply
    • Reply as topic
    Log in to reply
    This topic has been deleted. Only users with topic management privileges can see it.
    • B0M0A0Kundefined
      B0M0A0K
      last edited by

      Hi

      I have started seeing the error message "Error: M141: No chamber heater has been configured for slot 0" following an upgrade to the latest version of Ultimaker Cura (version 4.2.1). I see from other posts that this is an error message that can be ignored and that if you interrogate the gcode produced by Cura you can see the M141 line.

      This seems to be a new addition and I was wondering if anyone had managed to find the setting that triggers this message (so I can turn it off). It's that of [a]. Live with it or [b]. Manually edit the line out before every new print.

      ----------------------------------------------
      No fate but what we make ....
      1 Reply Last reply Reply Quote 0
      • Vetiundefined
        Veti
        last edited by

        have you set the g code flavor to reprap instead of marlin?

        1 Reply Last reply Reply Quote 0
        • B0M0A0Kundefined
          B0M0A0K
          last edited by

          Yes, g code flavor is set to RepRap.

          ----------------------------------------------
          No fate but what we make ....
          1 Reply Last reply Reply Quote 0
          • Vetiundefined
            Veti
            last edited by

            all plugins are up to date. specifically the duet one?

            B0M0A0Kundefined 1 Reply Last reply Reply Quote 0
            • grizewaldundefined
              grizewald
              last edited by

              Search Cura's settings for "Build Volume Temperature".

              Set it to zero.

              B0M0A0Kundefined 1 Reply Last reply Reply Quote 0
              • B0M0A0Kundefined
                B0M0A0K @Veti
                last edited by

                @veti Oh, I've not been using any plugins, didn't even know about the Duet plugin but will go take a look now. Thanks.

                ----------------------------------------------
                No fate but what we make ....
                1 Reply Last reply Reply Quote 0
                • B0M0A0Kundefined
                  B0M0A0K @grizewald
                  last edited by

                  @grizewald Thanks, unfortunately it is already set to zero.

                  ----------------------------------------------
                  No fate but what we make ....
                  grizewaldundefined 1 Reply Last reply Reply Quote 0
                  • grizewaldundefined
                    grizewald @B0M0A0K
                    last edited by

                    @b0m0a0k said in Error: M141: No chamber heater has been configured for slot 0:

                    @grizewald Thanks, unfortunately it is already set to zero.

                    That's odd. It fixed the problem for me.

                    1 Reply Last reply Reply Quote 0
                    • B0M0A0Kundefined
                      B0M0A0K
                      last edited by

                      OK, that's all fixed. I closed Cura and restarted, the entry appeared and this time contained the setting "28". I set this to zero and the message has gone. I looks like I either ignore future messages or just remember to go and set that entry to zero before proceeding.

                      ----------------------------------------------
                      No fate but what we make ....
                      grizewaldundefined 1 Reply Last reply Reply Quote 0
                      • grizewaldundefined
                        grizewald @B0M0A0K
                        last edited by

                        @b0m0a0k Last time I did this, after I'd replaced the 28 with 0, it stuck.

                        Of course, you'll have to check each profile as you use it because it seemed to set the default of 28 on all my profiles when I upgraded to 4.2.1. So it might seem that it came back again, but in reality it was just that I was using a profile where I hadn't checked if the setting was zero or not.

                        1 Reply Last reply Reply Quote 0
                        • First post
                          Last post
                        Unless otherwise noted, all forum content is licensed under CC-BY-SA