Navigation

    Duet3D Logo

    Duet3D

    • Register
    • Login
    • Search
    • Categories
    • Tags
    • Documentation
    • Order

    Stuck in spin loop, spinning module Network

    General Discussion
    2
    4
    452
    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.
    • MarMed
      MarMed last edited by

      Just had a reset mid print, not sure whats going on.

      Firmware Name: RepRapFirmware for Duet WiFi
      Firmware Electronics: Duet WiFi 1.0
      Firmware Version: 1.20 (2017-12-23)
      WiFi Server Version: 1.20
      Web Interface Version: 1.20

      M122
      === Diagnostics ===
      Used output buffers: 3 of 32 (9 max)
      === Platform ===
      RepRapFirmware for Duet WiFi version 1.20 running on Duet WiFi 1.0
      Board ID: 08DAM-999TL-MQ4S4-6J1F2-3S86L-94GHZ
      Static ram used: 15448
      Dynamic ram used: 98976
      Recycled dynamic ram: 264
      Stack ram used: 1392 current, 4384 maximum
      Never used ram: 12000
      Last reset 00:01:37 ago, cause: software
      Last software reset at 2018-01-14 05:27, reason: Stuck in spin loop, spinning module Network, available RAM 3848 bytes (slot 2)
      Software reset code 0x4041 HFSR 0x00000000, CFSR 0x00000000, ICSR 0x0041f80f, BFAR 0xe000ed38, SP 0x2001f9ac
      Stack: 0042c995 00008196 0043c277 00008196 ffffffe9 00001000 00081111 40080000 00008196 20002d8c 00437273 0043ab86 210b0200 3e1aa000 3e24de00 00000009 00000009 3e178897 45870070 438ff91a 44fc01bd 00000000 4964e1c0 44841fba
      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 28.4, current 29.7, max 31.4
      Supply voltage: min 0.8, current 0.9, max 4.0, under voltage events: 0, over voltage events: 0
      Driver 0: ok, SG min/max not available
      Driver 1: ok, SG min/max not available
      Driver 2: ok, SG min/max not available
      Driver 3: ok, SG min/max not available
      Driver 4: ok, SG min/max not available
      Date/time: 2018-01-14 05:29:51
      Cache data hit count 354749734
      Slowest main loop (seconds): 0.014096; fastest: 0.000035
      === 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 heaters = 0 -1 -1 -1, chamberHeaters = -1 -1
      Heater 1 is on, I-accum = 0.0
      === GCodes ===
      Segments left: 0
      Stack records: 2 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
      Failed messages: pending 0, notready 0, noresp 0
      WiFi firmware version 1.20
      WiFi MAC address 60:01:94:09:18:33
      WiFi Vcc 3.38, reset reason Turned on by main processor
      WiFi flash size 4194304, free heap 17232
      WiFi IP address 192.168.0.218
      WiFi signal strength -65dBm, reconnections 0, sleep mode modem
      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
      • dc42
        dc42 administrators last edited by

        Thanks, I'll look into it.

        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
        • dc42
          dc42 administrators last edited by

          I have taken a look. It appears to have got stuck in the SD card driver because a command failed to complete. I have seen at least one other occurrence of this.

          I have it in mind to add a timeout to that function to avoid the reset happening.

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

            @dc42:

            I have taken a look. It appears to have got stuck in the SD card driver because a command failed to complete. I have seen at least one other occurrence of this.

            I have it in mind to add a timeout to that function to avoid the reset happening.

            Thank you for taking the time to look into it, I forgot to include that I had tried to load the duet web control page to check on the printer's progress when the reset happened.

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