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

    Pause confusion...

    Scheduled Pinned Locked Moved
    General Discussion
    3
    4
    142
    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.
    • Chrissundefined
      Chriss
      last edited by

      Hi *,

      I'm a bit confused about the pause button in the DWC. I have a very complex start routine. Many things happen there and many of them take a looong time. My observation is that pressing the "pause" button does not have any effect here. Should that really be the case? I have a minimal start.g and source a macro file in the slicer start codes which includes a lot more files. The pause seems not to have any effect on that. I see the "spinning circle" for a while after I pressed the button but the printer continues it's exercise.

      My understanding is that the pause button triggers "M25", I send M25 via telnet with the same result.

      The M25 section directed me to "M226" which I tried too:

      M226
      Error: M226: use M226 and M601 only within a file being printed
      

      The funny thing is that M601 does not have a section in the docu:
      c2a8c6b0-617f-4e19-90c8-56665bbd92fd-image.png

      Anyway, I have the feeling that M25 times out in the background while my printer executes it's macros. Is my observation correct? Is that intentional?

      Board: Duet 3 Mini 5+ (Mini5plus)
      Firmware: RepRapFirmware for Duet 3 Mini 5+ 3.5.0-rc.3 (2024-01-24)
      Duet WiFi Server Version: 2.1beta7

      Cheers, Chriss

      oliofundefined 1 Reply Last reply Reply Quote 0
      • oliofundefined
        oliof @Chriss
        last edited by

        @Chriss it does not time out, but it's not jumping in front of the execution queue either. If you want to interrupt long moves, you may need to enable segmentation.

        <>RatRig V-Minion Fly Super5Pro RRF<> V-Core 3.1 IDEX k*****r <> RatRig V-Minion SKR 2 Marlin<>

        Chrissundefined 1 Reply Last reply Reply Quote 0
        • Chrissundefined
          Chriss @oliof
          last edited by

          @oliof

          Shouldn't the queue be longer than the current file? I'm sure that the pause did not even kicked in when one of the macro files ended and the FW jumped into a other one.

          Garth_42undefined 1 Reply Last reply Reply Quote 0
          • Garth_42undefined
            Garth_42 @Chriss
            last edited by

            @Chriss I know that using "R1" in an M98 call can change the behavior of a macro such that it can be interrupted. The behavior still isn't what you might expect though, reference the G-code dictionary. I haven't tested calling g-code files within another g-code file using M98 and seeing if those can be paused.

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