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

    Pause during Tool-Change impossible to resume

    Scheduled Pinned Locked Moved
    Beta Firmware
    2
    2
    125
    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.
    • NineMileundefined
      NineMile
      last edited by

      I had a "Pause" option at the end of my guided tool-change procedure that runs M25 from tpost.g.

      This executes correctly, putting the running job into the "Paused" state, but it appears impossible to Resume the job - it looks like the M24 command sent from DWC when clicking "Resume" spins eternally, and this also means the job cannot then be cancelled - the only recovery is to run M999 to restart.

      My pause / resume functionality works perfectly when the pause is not called from within a tool change so I know that the functionality in those files is not the (direct) cause.

      This functionality isn't important for my actual usage so I have removed the pause option at the end of the tool change for now, but given that it puts the machine into what appears to be an unrecoverable state it would maybe make sense to not process M25 within toolchange files, or make sure the machine can be subsequently resumed.

      M122 below:

      === Diagnostics ===
      RepRapFirmware for STM32F4 based Boards (fysetc_spider_king407) version 3.5.0-rc.3+101 (2024-01-28 17:56:35) running on STM32F4 (standalone mode)
      Board ID: 610A3-0427A-GA3TW-6N1FN-Z7YSY-70000
      Used output buffers: 1 of 40 (31 max)
      === RTOS ===
      Static ram: 20140
      Dynamic ram: 99356 of which 60 recycled
      Never used RAM 10488, free system stack 113 words
      CCMRam static ram: 24628 dynamic ram: 38012 free ram 2892
      Tasks: NETWORK(1,ready,8.1%,162) HEAT(3,nWait 6,0.0%,405) Move(4,nWait 6,0.0%,283) TMC22xx(4,delaying,1.1%,113) TMC51xx(4,delaying,2.6%,139) FSWRITE(2,nWait 4,0.0%,474) MAIN(1,running,87.7%,529) IDLE(0,ready,0.4%,29), total 100.0%
      Owned mutexes: WiFi(NETWORK) USB(MAIN)
      === Platform ===
      Last reset 00:45:32 ago, cause: power on/off
      Last software reset at 2024-03-07 10:07, reason: User, Gcodes spinning, available RAM 13336, slot 1
      Software reset code 0x0003 HFSR 0x00000000 CFSR 0x00000000 ICSR 0x00400000 BFAR 0xe000ed38 SP 0x00000000 Task MAIN Freestk 0 n/a
      Error status: 0x00
      MCU temperature: min 40.0, current 40.1, max 40.4
      Supply voltage: min 24.0, current 24.0, max 24.0, under voltage events: 0, over voltage events: 0, power good: yes
      Heap OK, handles allocated/used 198/98, heap memory allocated/used/recyclable 4096/2880/1128, gc cycles 79
      Events: 3 queued, 3 completed
      Driver 0: standstill 5160, SG min n/a, mspos 900, reads 54110, writes 0
      Driver 1: standstill 5160, SG min n/a, mspos 852, reads 54111, writes 0
      Driver 2: not present
      Driver 3: not present
      Driver 4: standstill 2209, SG min 6, reads 6252, writes 0
      Driver 5: not present
      Driver 6: not present
      Driver 7: not present
      Driver 8: not present
      Driver 9: not present
      Driver 10: 
      Driver 11: 
      Driver 12: 
      Driver 13: 
      Date/time: 2024-03-13 10:44:28
      Slowest loop: 10.48ms; fastest: 0.08ms
      === Storage ===
      Free file entries: 16
      SD card 0 detected
      SD card longest read time 2.9ms, write time 0.0ms, max retries 0
      === Move ===
      DMs created 83, segments created 6, maxWait 0ms, bed compensation in use: none, height map offset 0.000, max steps late 0, ebfmin 0.00, ebfmax 0.00
      no step interrupt scheduled
      Moves shaped first try 0, on retry 0, too short 0, wrong shape 0, maybepossible 0
      === DDARing 0 ===
      Scheduled moves 11, completed 11, hiccups 0, stepErrors 0, LaErrors 0, Underruns [0, 0, 0], CDDA state -1
      === DDARing 1 ===
      Scheduled moves 0, completed 0, hiccups 0, stepErrors 0, LaErrors 0, Underruns [0, 0, 0], CDDA state -1
      === Heat ===
      Bed heaters -1 -1 -1 -1, chamber heaters -1 -1 -1 -1, ordering errs 0
      === GCodes ===
      Movement locks held by File, null
      HTTP is doing "M24" in state(s) 0
      File is idle in state(s) 0 19, running macro
      USB is ready with "M122" in state(s) 0
      Aux is idle in state(s) 0
      Trigger is idle in state(s) 0
      Queue is idle in state(s) 0
      LCD is idle in state(s) 0
      Daemon is doing "G4 P{global.mosDAEUR}" in state(s) 0 0, running macro
      Autopause is idle in state(s) 0
      File2 is idle in state(s) 0, sync state 2
      Queue2 is idle in state(s) 0
      Q0 segments left 0, axes/extruders owned 0x0000007
      Code queue 0 is empty
      Q1 segments left 0, axes/extruders owned 0x0000000
      Code queue 1 is empty
      === CAN ===
      Disabled
      Longest wait 0ms for reply type 0, peak Tx sync delay 0 free buffers 0 (min 0), ts 0/0/0
      Tx timeouts 0,0,0,0,0,0
      === Network ===
      Slowest loop: 20.85ms; fastest: 0.09ms
      Responder states: MQTT(0) HTTP(0) HTTP(0) HTTP(0) HTTP(0) FTP(0)
      HTTP sessions: 1 of 8
      Uploads/Errors: 0/0
      === WiFi ===
      Interface state: active
      Module is connected to access point 
      Failed messages: pending 0, notrdy 0, noresp 0
      Bad header: 0/0
      Firmware version 2.1beta6-01
      MAC address e8:31:cd:c1:3e:8c
      Module reset reason: Power up, Vcc 0.00, flash size 4194304, free heap 187768
      WiFi IP address 10.3.142.134
      Signal strength -38dBm, channel 1, mode 802.11n, reconnections 0
      Clock register 00003043
      Socket states: 0 0 0 0 0 0 0 0
      ok
      
      dc42undefined 1 Reply Last reply Reply Quote 0
      • dc42undefined
        dc42 administrators @NineMile
        last edited by

        @NineMile you are correct, pausing during tool changes (or more generally, during macros) isn't supported.

        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