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

    M400 / G4 P0 Not working?

    Scheduled Pinned Locked Moved
    Beta Firmware
    3
    19
    579
    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.
    • RobMinkundefined
      RobMink @dc42
      last edited by RobMink

      @dc42

      Thanks for the info!

      If I run the command M98 P"tpre3.g" it works, but if I just go T0 T3 it does not. T0 will load correctly the first time, then exhibit the same behavior. I apologize if this is a bug on my end!

      EDIT: I tried plugging the duet into my laptop and running pronterface. I get "Board 1 does not have input handle 1000" when I try and home until I reboot the printer afterwards.

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

        @RobMink said in M400 / G4 P0 Not working?:

        If I run the command M98 P"tpre3.g" it works, but if I just go T0 T3 it does not. T0 will load correctly the first time, then exhibit the same behavior. I apologize if this is a bug on my end!

        No bug at your end, I'm just trying to identify the circumstances that cause the problem. Did you have a chance to try standalone mode? EDIT: and/or getting a debug trace from RRF as chrishamm suggested.

        EDIT: I tried plugging the duet into my laptop and running pronterface. I get "Board 1 does not have input handle 1000" when I try and home until I reboot the printer afterwards.

        That message normally means that the expansion board was reset (e.g. because of a firmware update, reset button being pressed, or firmware crash) and config.g hasn't been run since then. If you think this problem is reproducible without a deliberate reset, please let us know and post the result of M122 and M112 B1.

        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
        • RobMinkundefined
          RobMink
          last edited by RobMink

          I tried a USB connection again, and this time it (USB) worked. Not sure what caused the issue the first time.

          SENDING:M111 P3 S1
          Debugging enabled for modules: GCodes(3)
          Debugging disabled for modules: Platform(0) Network(1) Webserver(2) Move(4) Heat(5) DDA(6) Roland(7) Scanner(8) PrintMonitor(9) Storage(10) PortControl(11) DuetExpansion(12) FilamentSensors(13) WiFi(14) Display(15) LinuxInterface(16)
          >>> T0
          SENDING:T0
          USB: T0
          USB: G1 X96 Y760 F5000
          USB: G1 Y830 F2400
          USB: M400
          USB: M280 P0 S150
          USB: G4 P500
          USB: G1 Y800 F2400
          USB: G1 Y760 F3600
          USB: M116 P0
          USB: M105
          >>> T3
          SENDING:T3
          USB: T3
          USB: G1 X96 Y760 F5000
          USB: G1 Y800 F1200
          USB: M280 P0 S40
          USB: G1 Y830 F2400
          USB: G1 Y760 F2400
          Queue: M280 P0 S40
          USB: G1 X306 Y760 F5000
          USB: G1 Y830 F2400
          USB: M400
          USB: M280 P0 S150
          USB: G4 P400
          USB: G1 Y800 F2400
          USB: G1 Y760 F3600
          USB: M105
          

          All the edits! Oops!

          Ok, so a little clarification, the tool 0 docking in the last chunk after T3 ends at USB: G1 Y760 F2400 and T3 picks up at USB: G1 X306 Y760 F5000

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

            Thanks. You sent the T0 and T3 commands from USB this time. Did the problem occur when you selected T0, with no tool initially selected? Did it occur when you changed from T0 to T3?

            I think I've spotted a problem:

            T3
            SENDING:T3
            USB: T3
            USB: G1 X96 Y760 F5000
            USB: G1 Y800 F1200
            USB: M280 P0 S40
            USB: G1 Y830 F2400
            USB: G1 Y760 F2400
            Queue: M280 P0 S40
            ; T0 finished docking at this point
            USB: G1 X306 Y760 F5000
            USB: G1 Y830 F2400
            USB: M400
            USB: M280 P0 S150
            USB: G4 P400
            USB: G1 Y800 F2400
            USB: G1 Y760 F3600
            USB: M105

            What I think is happening is that you have a M280 P0 S40 command in tfree.g and it is that command that is still being executed when the next tpre is run. RRF can't tell when the servo has finished responding to that command.

            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
            • RobMinkundefined
              RobMink
              last edited by RobMink

              It happend after I went from T0 to T3.

              M280 P0 S40 is the tool release command, and the M280 P0 S150 tool grab command happens before the printer isin position to grab the tool.

              Here is

              ; tfree0.g
              ; called when tool 0 is freed
              G1 X96 Y760 F5000 
              G1 Y800 F1200
              M280 P0 S40
              G1 Y830 F2400
              G1 Y760	F2400
              

              Should I put a G4 P1000 or something in the end of this file and test?

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

                @RobMink said in M400 / G4 P0 Not working?:

                It happend after I went from T0 to T3.

                M280 P0 S40 is the tool release command, and the M280 P0 S150 tool grab command happens before the printer isin position to grab the tool.

                Here is

                ; tfree0.g
                ; called when tool 0 is freed
                G1 X96 Y760 F5000 
                G1 Y800 F1200
                M280 P0 S40
                G1 Y830 F2400
                G1 Y760	F2400
                

                Should I put a G4 P1000 or something in the end of this file and test?

                Yes please, assuming 1 sec is long enough for the servo. Or put it directly after the M280 command, if you want the servo move to complete before the G1 Y830 command.

                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
                • RobMinkundefined
                  RobMink
                  last edited by

                  Ok, I gave that a go. It releases the tool correctly and pulls back, pauses, but does the 'grab' command (M280 P0 S150) for T3 en route to T3. I can post a video if that would help.

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

                    Thanks. I'll see if I can reproduce that. I may ask for a video later.

                    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
                    • RobMinkundefined
                      RobMink
                      last edited by RobMink

                      Upgrading all using a sudo apt-get/apt-upgrade to RC10 and removing the M400 fixed the issue.

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

                        @RobMink said in M400 / G4 P0 Not working?:

                        Upgrading all using a sudo apt-get/apt-upgrade to RC10 and removing the M400 fixed the issue.

                        Thanks, I suspected that it might because of this bug fix:

                        • Non-movement commands that needed to be synchronised to the movement queue were sometimes executed too early

                        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

                        RobMinkundefined 1 Reply Last reply Reply Quote 0
                        • RobMinkundefined
                          RobMink @dc42
                          last edited by

                          @dc42

                          Yep! Thanks for all the great work! I thought it would give it a shot when I saw that release note.

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