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

    My DeltaD3H (DIY Delta printer)

    Scheduled Pinned Locked Moved
    My Duet controlled machine
    6
    24
    3.1k
    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.
    • DannerD3Hundefined
      DannerD3H
      last edited by

      Hmm it seems that i do not even have a config-override.g file..

      Is this file a must have?

      1 Reply Last reply Reply Quote 0
      • dc42undefined
        dc42 administrators
        last edited by

        No, it's not a must-have.

        Are you finding the Z=0 nozzle position too high immediately after you run auto calibration, or only after you have restarted and homed the printer again?

        Please post your config.g and bed.g files.

        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
        • DannerD3Hundefined
          DannerD3H
          last edited by

          Aaaah found my error. I had two G31 commands in the config.g file. Srry that was a stupid question then.

          I am still getting used to this duet way of doing things. It is really clever once you get the hang of it!

          1 Reply Last reply Reply Quote 0
          • DannerD3Hundefined
            DannerD3H
            last edited by

            Hello again!

            Does anyone know how i can make my machine turn on (send M80) before the machine heats up?
            I am using Simplify3D as a slicer. The problem is S3D inserts heating commands (and wait until heated) before my start-script. This means that the printer will try to reach bed temp without power, thus never getting to my M80 command from my start code.
            I have read something on S3D's forum:

            But i am not clever enough to understand what to put in my M140 and M104 so that i don't have to change it every time..
            Currently this is my startscript:

            [[language]]
            M80	;Turn on
            
            G28 		;Home all axes
            G32		;Auto calibration
            G29 S1		;Load height map
            
            

            This is what the slicer outputs:

            [[language]]
            G90
            M83
            M106 S255
            G4 P500
            M106 S0
            M140 S60
            M190 S60
            M104 S200 T0
            M109 S200 T0
            M80		:Turn on
            G28 		;Home all axes
            G32		;Auto calibration
            G29 S1		;Load height map
            
            

            Another question:
            My printer always makes a short pause of 1-2 seconds between the first and second layer. does anyone know why this is? (The fans start on the third layer).

            1 Reply Last reply Reply Quote 0
            • DannerD3Hundefined
              DannerD3H
              last edited by

              Any ideas? 🙂

              1 Reply Last reply Reply Quote 0
              • dc42undefined
                dc42 administrators
                last edited by

                What I think you need to include in your start gcode is:

                T0 ; select tool 0
                M140 S[bed_temperature] ; set bed temperature
                M104 S[extruder0_temperature] ; set extruder temperature
                M116 ; wait for temperatures to be reached

                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
                • EasyTargetundefined
                  EasyTarget
                  last edited by

                  @DannerD3H:

                  My printer always makes a short pause of 1-2 seconds between the first and second layer. does anyone know why this is? (The fans start on the third layer).

                  If the temperature changes (first layer hotter than others) then maybe this is another forced pause until the head has cooled to the new temp?
                  PS: Lovely printer, the pop out electronics bay makes me jealous..

                  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
                  • DannerD3Hundefined
                    DannerD3H
                    last edited by

                    Thank you easy target!
                    But don't be jealous.. It seemed like a good idea on the drawing but in reality it is not! It makes proper wire management near impossible as all wires have to be at least 30 cm to long to be able to pull out the tray.. I will most likely ditch it and mount the board permanently instead.

                    I have a constant temperature all the way so shouldn't be the case.. Will look closely on the g-code tomorrow to see if I can figure out whether it's a slicer or firmware thing..

                    Dc42, if I do that, won't I then have to change something in the start code to use my second nozzle?
                    If I ever have to change values on the start code, then I would rather turn on the machine manually first.. But would be cool if starting a print automatically would send the m80 command before executing any of the print file…

                    1 Reply Last reply Reply Quote 0
                    • number40fanundefined
                      number40fan
                      last edited by

                      You could always edit the .gcode in a text editor and put the M80 in front of everything. Little time consuming, but should get the job done.

                      1 Reply Last reply Reply Quote 0
                      • dc42undefined
                        dc42 administrators
                        last edited by

                        I have often thought that slicers should support 2 sets of start gcode: one to execute right at the start, and one after the slicer has generated the temperature-setting code before the print starts.

                        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
                        • DannerD3Hundefined
                          DannerD3H
                          last edited by

                          Yes but the post processing of the g-codes are exactly what i want to avoid..

                          DC42, yes either that or at least a setting so that the slicer would automatically include the m80 command as the first command..
                          Is this something that can be implemented in the Duet web interface? Could it be implemented that every time you start a print, the web interface would send a M80, like when i manually press the ATX on button?

                          I n´know it may seem like a silly small thing, but it would just be a nayz feature i think..

                          1 Reply Last reply Reply Quote 0
                          • dc42undefined
                            dc42 administrators
                            last edited by

                            I guess there could be a start.g macro run when you start printing a file from SD card.

                            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
                            • DannerD3Hundefined
                              DannerD3H
                              last edited by

                              Is this something that is already possible or ?

                              1 Reply Last reply Reply Quote 0
                              • DannerD3Hundefined
                                DannerD3H
                                last edited by

                                I finally got to make some prints this weekend. I think this could become a really good printer, but i still have a few issues..

                                This thread is covering my two biggest issues: https://www.duet3d.com/forum/thread.php?pid=37203#p37203

                                1 Reply Last reply Reply Quote 0
                                • dc42undefined
                                  dc42 administrators
                                  last edited by

                                  @DannerD3H:

                                  Is this something that is already possible or ?

                                  Not yet, but I will consider it for the next 1.21RC.

                                  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
                                  • DannerD3Hundefined
                                    DannerD3H
                                    last edited by

                                    Cool! 🙂

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