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

    Random restarts mid-print. M122 included.

    Scheduled Pinned Locked Moved
    General Discussion
    4
    6
    836
    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.
    • Yogiundefined
      Yogi
      last edited by

      Hello all,

      I've recently built a second printer and went with a Duet wifi for the build. So far I've put maybe 100 hours of print in it with no issues however now I'm getting random resets mid print.

      Things will be going well then I'll hear the click click click of the bltouch doing it's startup self test. That's when I find the printer just stopped. The M122 is below, any help would be fantastic. Thank you!

      M122
      === Diagnostics ===
      Used output buffers: 3 of 32 (10 max)
      === Platform ===
      RepRapFirmware for Duet WiFi version 1.19.2 running on Duet WiFi 1.0
      Board ID: 08DGM-95BLL-N6PSS-6J1F6-3S86N-K0TRM
      Static ram used: 21176
      Dynamic ram used: 96392
      Recycled dynamic ram: 1216
      Stack ram used: 1304 current, 4992 maximum
      Never used ram: 7296
      Last reset 00:02:13 ago, cause: power up
      Last software reset reason: User, spinning module GCodes, available RAM 7376 bytes (slot 1)
      Software reset code 0x0003, HFSR 0x00000000, CFSR 0x00000000, ICSR 0x00400000, BFAR 0xe000ed38, SP 0xffffffff
      Error status: 0
      Free file entries: 10
      SD card 0 detected, interface speed: 20.0MBytes/sec
      SD card longest block write time: 0.0ms
      MCU temperature: min 23.3, current 25.3, max 26.5
      Supply voltage: min 24.1, current 24.2, max 24.5, under voltage events: 0, over voltage events: 0
      Driver 0: standstill
      Driver 1: standstill
      Driver 2: standstill
      Driver 3: standstill
      Driver 4: standstill
      Date/time: 2018-04-10 18:50:55
      Slowest main loop (seconds): 0.004196; fastest: 0.000034
      === Move ===
      MaxReps: 0, StepErrors: 0, FreeDm: 240, MinFreeDm 240, MaxWait: 0ms, Underruns: 0, 0
      Scheduled moves: 0, completed moves: 0
      Bed compensation in use: none
      Bed probe heights: 0.000 0.000 0.000 0.000 0.000
      === Heat ===
      Bed heater = 0, chamber heater = -1
      === GCodes ===
      Segments left: 0
      Stack records: 1 allocated, 0 in use
      Movement lock held by null
      http is idle in state(s) 0
      telnet is idle in state(s) 0
      file is idle in state(s) 0
      serial is idle in state(s) 0
      aux is idle in state(s) 0
      daemon is idle in state(s) 0
      queue is idle in state(s) 0
      autopause is idle in state(s) 0
      Code queue is empty.
      Network state is running
      WiFi module is connected to access point
      WiFi firmware version 1.19.2
      WiFi MAC address 2c:3a:e8:0b:07:cd
      WiFi Vcc 3.09, reset reason Turned on by main processor
      WiFi flash size 4194304, free heap 39224
      WiFi IP address 192.168.1.75
      WiFi signal strength -58dBm
      Reconnections 0
      HTTP sessions: 1 of 8
      Socket states: 2 0 0 0 0 0 0 0
      Responder states: HTTP(1) HTTP(0) HTTP(0) HTTP(0) FTP(0) Telnet(0)

      1 Reply Last reply Reply Quote 0
      • number40fanundefined
        number40fan
        last edited by

        My first thought is a power supply issue.

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

          @number40fan said in Random restarts mid-print. M122 included.:

          My first thought is a power supply issue.

          I agree, the clue is in this part of the M122 report:

          Last reset 00:02:13 ago, cause: 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
          • Yogiundefined
            Yogi
            last edited by

            Dang, thank you for the help!

            It's a new meanwell, I tried not to skimp on the psu.

            whosrdaddyundefined 1 Reply Last reply Reply Quote 0
            • whosrdaddyundefined
              whosrdaddy @Yogi
              last edited by whosrdaddy

              Could be a cabling issue, did you check that your VIN Connector cable is still firmly attached to the board and PSU?

              1 Reply Last reply Reply Quote 0
              • Yogiundefined
                Yogi
                last edited by

                It's all nice and secure, Vin stays right at and sometimes slightly above 24.0v

                Only had this problem about 3 times in a row then now its running fine again.

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