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

Preheat button

Scheduled Pinned Locked Moved
Duet Web Control wishlist
6
7
1.7k
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.
  • undefined
    Duetplicator
    last edited by 15 Feb 2018, 13:58

    I would like to see a "Preheat" button, could be in the G-Code files section, next to each of the files to print. So if you print with all sorts of filament (and thus different temps), making it easier to preheat to the right temp.

    Cheers
    -Kim

    1 Reply Last reply Reply Quote 0
    • undefined
      Dougal1957
      last edited by 15 Feb 2018, 14:06

      Macros are for this sort of thing I also save all my Gcodes files on the SD Card in folders for projects/filament so it is easy to see which one to use.

      1 Reply Last reply Reply Quote 0
      • undefined
        EasyTarget
        last edited by 15 Feb 2018, 16:27

        Macros are one way of doing this for sure but..
        The octoprint model; where you can load a model file without immediately starting the print is nice; combined with the preheat button plugin I can load the print, hit preheat, get ready (delta calibrate, change filaments, maybe use the gcode viewer to make sure it looks sane) and then hit print. It's a nice workflow to use.

        Disaster? The original Printeye is dying with RRF 3.5 (M208 depreciated).
        PrintPy2024 to the rescue!
        MicroPython based; with simple wiring and and no custom PCB.

        1 Reply Last reply Reply Quote 0
        • undefined
          Phaedrux Moderator
          last edited by 15 Feb 2018, 16:38

          Agreed. I just created preheat macros for the various filament types I use, but I do miss the preheat plugin from Octoprint where you could upload a gcode, it would automatically queue up the most recently uploaded file, and then have a preheat button to get the bed and nozzle up to temp while preparing the rest of the printer. There's also a plugin to turn off any heaters if the print hasn't been started within a configurable time frame, in case you actually forget to start the print.

          Z-Bot CoreXY Build | Thingiverse Profile

          1 Reply Last reply Reply Quote 0
          • undefined
            dc42 administrators
            last edited by 15 Feb 2018, 16:47

            Would someone like to specify exactly what preheat would do? Bearing in mind that we have single nozzle, single head dual nozzle, IDEX and mixing extruder configurations.

            I envisage that RRF would execute the GCode file in simulation mode, except that tool selection commands would be actioned (with or without running the tool change files?) and heating commands would be actioned but without waiting for temperatures. But there may be specific printer configurations that need something a little more complicated.

            Duet WiFi hardware designer and firmware engineer
            Please do not ask me for Duet support via PM or email, use the forum
            http://www.escher3d.com, https://miscsolutions.wordpress.com

            1 Reply Last reply Reply Quote 0
            • undefined
              EasyTarget
              last edited by 15 Feb 2018, 16:54

              I hadn't thought that far 🙂 for me I'd be happy if t simply picked all temperatures that would be set/achieved before the first extrusion move, and applied those. But then I'd only though about my single-extruder machines, I can see it's not quite as simple as I'd imagined..

              Disaster? The original Printeye is dying with RRF 3.5 (M208 depreciated).
              PrintPy2024 to the rescue!
              MicroPython based; with simple wiring and and no custom PCB.

              1 Reply Last reply Reply Quote 0
              • undefined
                garyd9
                last edited by 15 Feb 2018, 17:13

                @dc42:

                Would someone like to specify exactly what preheat would do? Bearing in mind that we have single nozzle, single head dual nozzle, IDEX and mixing extruder configurations.

                Step through the gcode file to find the first temperatures that are waited for and set them. Would likely need to go through the simulation routines to determine the active/standby temperatures needed for specific tools (and which tools are active) once any 'wait' type command is encountered.

                In my opinion, it should stop at the FIRST command that causes a wait and preheat based on the values set at that point. So, if the gcode file sets only the bed temp and waits for it, then ONLY the bed temperature would be preheated. (In that case, it'd probably be a good idea to set tools to standby temps without waiting before waiting on the bed temp - this causing the tools to be preheated to standby at the same time as the bed is preheated.)

                Here's some examples off the top of my head:

                G10 (with R/S parameters) followed by M116
                M104 followed by M116
                M109
                M140 followed byM116
                M141 followed by M141
                M190
                M191

                NOTE: preheated stuff will cause a bug to be hit that I've reported elsewhere concerning M116 commands being ignored.

                "I'm not saying that you are wrong - I'm just trying to fit it into my real world simulated experience."

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