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

    RRF 3.2 Beta 1 not recovering from Pause event

    Scheduled Pinned Locked Moved
    Beta Firmware
    6
    7
    347
    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.
    • jay_s_ukundefined
      jay_s_uk
      last edited by jay_s_uk

      I am running RR3 3.2 beta 1 on a duet 3 with SBC
      DSF Version 3.2.0-beta1+1
      DWC Version 3.2.0-beta1+2

      I've been changing slicer and as of yet, its not waiting for the tool to heat on beginning a print. To mitigate that, once the print begins, I pause the print until the tool is at the correct temperature.
      On resuming the print, nothing happens.

      Here is an output from M122

      m122
      === Diagnostics ===
      RepRapFirmware for Duet 3 MB6HC version 3.2-beta1 running on Duet 3 MB6HC v0.6 or 1.0 (SBC mode)
      Board ID: 08DJM-956L2-G43S4-6J1DL-3SJ6N-186LG
      Used output buffers: 1 of 40 (14 max)
      === RTOS ===
      Static ram: 154820
      Dynamic ram: 135280 of which 44 recycled
      Exception stack ram used: 528
      Never used ram: 102544
      Tasks: HEAT(blocked,276) CanReceiv(blocked,874) CanSender(blocked,336) CanClock(blocked,352) TMC(blocked,18) MAIN(running,719) IDLE(ready,19)
      Owned mutexes:
      === Platform ===
      Last reset 05:35:03 ago, cause: software
      Last software reset at 2020-09-17 08:01, reason: User, LinuxInterface spinning, available RAM 103272, slot 0
      Software reset code 0x0010 HFSR 0x00000000 CFSR 0x00000000 ICSR 0x0444a000 BFAR 0x00000000 SP 0xffffffff Task MAIN
      Error status: 0x020
      MCU temperature: min 31.6, current 34.5, max 35.9
      Supply voltage: min 26.8, current 27.0, max 27.1, under voltage events: 0, over voltage events: 0, power good: yes
      12V rail voltage: min 11.3, current 12.1, max 12.1, under voltage events: 0
      Driver 0: position -12322, standstill, reads 60649, writes 8 timeouts 0, SG min/max 0/1023
      Driver 1: position -4724, standstill, reads 60649, writes 8 timeouts 0, SG min/max 0/1023
      Driver 2: position 45121, standstill, reads 60646, writes 10 timeouts 0, SG min/max 0/1023
      Driver 3: position 8740, standstill, reads 60647, writes 10 timeouts 0, SG min/max 0/1023
      Driver 4: position 0, standstill, reads 60647, writes 10 timeouts 0, SG min/max 0/1023
      Driver 5: position 0, standstill, reads 60647, writes 10 timeouts 0, SG min/max 0/1023
      Date/time: 2020-09-17 13:37:02
      Slowest loop: 7.91ms; fastest: 0.21ms
      === Storage ===
      Free file entries: 10
      SD card 0 not detected, interface speed: 37.5MBytes/sec
      SD card longest read time 0.0ms, write time 0.0ms, max retries 0
      === Move ===
      Hiccups: 0(0), FreeDm: 375, MinFreeDm: 324, MaxWait: 13507717ms
      Bed compensation in use: mesh, comp offset 0.000
      === MainDDARing ===
      Scheduled moves: 82, completed moves: 82, StepErrors: 0, LaErrors: 0, Underruns: 0, 0  CDDA state: -1
      === AuxDDARing ===
      Scheduled moves: 0, completed moves: 0, StepErrors: 0, LaErrors: 0, Underruns: 0, 0  CDDA state: -1
      === Heat ===
      Bed heaters = 0 -1 -1 -1 -1 -1 -1 -1 -1 -1 -1 -1, chamberHeaters = -1 -1 -1 -1
      Heater 0 is on, I-accum = 0.6
      Heater 2 is on, I-accum = 0.0
      === GCodes ===
      Segments left: 0
      Movement lock held by null
      HTTP* is ready with "M122" in state(s) 0
      Telnet is idle in state(s) 0
      File* is idle in state(s) 0
      USB is idle 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
      SBC is idle in state(s) 0
      Daemon* is idle in state(s) 0
      Aux2 is idle in state(s) 0
      Autopause is idle in state(s) 0
      Code queue is empty.
      === Network ===
      Slowest loop: 0.00ms; fastest: 5726623.00ms
      Responder states:
      HTTP sessions: 0 of 8
      - Ethernet -
      State: disabled
      Error counts: 0 0 0 0 0
      Socket states: 0 0 0 0 0 0 0 0
      === CAN ===
      Messages sent 156069, send timeouts 156069, longest wait 5ms for type 6029, free CAN buffers 48
      === SBC interface ===
      State: 0, failed transfers: 0
      Last transfer: 18ms ago
      RX/TX seq numbers: 45968/45970
      SPI underruns 0, overruns 0
      Number of disconnects: 0
      Buffer RX/TX: 0/0-0
      === Duet Control Server ===
      Duet Control Server v3.2.0-beta1+1
      Code buffer space: 4096
      Configured SPI speed: 8000000 Hz
      Full transfers per second: 31.63
      File /opt/dsf/sd/gcodes/Inch - Spur gear 14DP 16T 20PA 0.5FW ---S16N3.0H2.0L0.375N.gcode is selected, processing
      

      Owns various duet boards and is the main wiki maintainer for the Teamgloomy LPC/STM32 port of RRF. Assume I'm running whatever the latest beta/stable build is

      1 Reply Last reply Reply Quote 0
      • Lucasundefined
        Lucas
        last edited by

        Hello,

        I have a similar issue. I paused a print, the tool goes back to X0 Y0 as expected then I resumed the print, the tool goes back to the last printing position and stays there.

        I tried to pause and resume multiple times but the print never continued, I had to stop it.

        1 Reply Last reply Reply Quote 0
        • observatoerundefined
          observatoer
          last edited by

          Same here. Goes back to last printing position and stops there.

          1 Reply Last reply Reply Quote 0
          • Sotidiiundefined
            Sotidii
            last edited by

            Same here. Goes back to last printing position and stops there.

            1 Reply Last reply Reply Quote 0
            • chrishammundefined
              chrishamm administrators
              last edited by

              Thanks for the report, I am looking into it.

              Duet software engineer

              1 Reply Last reply Reply Quote 0
              • docboboundefined
                docbobo
                last edited by

                Same problem for me with M600: filament-change.g is executed and the extruder is moved to the desired position. When resuming the print, the extruder us moved back to its original position and nothing happens.

                Then, after a while, I get a "Finished Printing" notification.

                1 Reply Last reply Reply Quote 0
                • chrishammundefined
                  chrishamm administrators
                  last edited by

                  I was able to find the reason for this and it is going to be fixed in 3.2-b2.

                  Duet software engineer

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