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

    Problem with powering on with M80

    Scheduled Pinned Locked Moved
    Tuning and tweaking
    3
    10
    1.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.
    • dekundefined
      dek
      last edited by

      I'm trying to have the printer power on when I send it a file to print from Cura with the DuetRRF plugin. I'm sending the M80 in the start script but this doesn't work because I'm guessing it needs to power on earlier than this in the printing process. Is there any way of trigger the M80 when the printer receives a print command?

      1 Reply Last reply Reply Quote 0
      • Vetiundefined
        Veti
        last edited by

        Did you open the gcode and look where the M80 command is?
        in slicer i have it as the first command in start g code and its working fine.

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

          You might need to include a G4 delay command after the M80 command to give the stepper drivers time to power up.

          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
          • dekundefined
            dek
            last edited by

            I have the start script stored on the duet and referencing it in the slicer with "M98 P/macros/Scripts/start.g"

            And start.g starts with:
            M80 ; Power On
            G4 S5 ; Dwell for 5 seconds

            But the printer doesn't even power up. However, sending the M80 command in the G-code console works.

            dc42undefined 1 Reply Last reply Reply Quote 0
            • Vetiundefined
              Veti
              last edited by

              try adding the m80 directly

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

                @dek said in Problem with powering on with M80:

                I have the start script stored on the duet and referencing it in the slicer with "M98 P/macros/Scripts/start.g"

                And start.g starts with:
                M80 ; Power On
                G4 S5 ; Dwell for 5 seconds

                But the printer doesn't even power up. However, sending the M80 command in the G-code console works.

                Is the M98 command right at the start of the GCode file generated by the slicer? I have a suspicion that if you look, you will find there there are some heating commands before it.

                Have you tried putting the M80 command in file /sys/start.g file instead? That script is run automatically when you start a print from SD card, unless you are using old firmware.

                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

                dekundefined 1 Reply Last reply Reply Quote 0
                • Vetiundefined
                  Veti
                  last edited by

                  This is how my printer starts in cura. if you dont include the 104 140 109 cura will generate them before the m80 command.

                  M80
                  M104 S{material_print_temperature_layer_0, 0} ;Start heating extruder
                  M140 S{material_bed_temperature_layer_0, 0} ;Start heating bed
                  M109 S{material_print_temperature_layer_0, 0} ;Wait for extruder to reach temp before proceeding

                  1 Reply Last reply Reply Quote 0
                  • dekundefined
                    dek @dc42
                    last edited by

                    @dc42 said in Problem with powering on with M80:

                    @dek said in Problem with powering on with M80:

                    I have the start script stored on the duet and referencing it in the slicer with "M98 P/macros/Scripts/start.g"

                    And start.g starts with:
                    M80 ; Power On
                    G4 S5 ; Dwell for 5 seconds

                    But the printer doesn't even power up. However, sending the M80 command in the G-code console works.

                    Is the M98 command right at the start of the GCode file generated by the slicer? I have a suspicion that if you look, you will find there there are some heating commands before it.

                    Have you tried putting the M80 command in file /sys/start.g file instead? That script is run automatically when you start a print from SD card, unless you are using old firmware.

                    Yes, this worked! Thank you!

                    As Veti said I think the problem was that Cura generated the commands in the wrong order. By a start.g in the sys directory I can still keep it simple in the slicer. This will make switching between different slicers easier.

                    1 Reply Last reply Reply Quote 0
                    • Vetiundefined
                      Veti
                      last edited by

                      dont forget the M81 S1 in the end code

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

                        @veti said in Problem with powering on with M80:

                        dont forget the M81 S1 in the end code

                        ...or in stop.g.

                        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
                        • First post
                          Last post
                        Unless otherwise noted, all forum content is licensed under CC-BY-SA