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

    Duet2 reboots at random time

    Scheduled Pinned Locked Moved
    Duet Hardware and wiring
    2
    4
    181
    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.
    • ShOrTyundefined
      ShOrTy
      last edited by

      Hello everyone,
      my Duet2 started to reboot at random times.
      I thought it would be the board, but i switched it and the problem remains.
      Basically i have some faulty peripheral.
      Connected to the board i have limit switches, stepper motors, thermistors and resistors...

      Well a faulty limit switch would give a false signal nothing more, a faulty thermistor would give false temperature values, a faulty resistor would not heat up ... so basically my question is, could a faulty stepper motor reset the board??

      1 Reply Last reply Reply Quote 0
      • SIamundefined
        SIam
        last edited by SIam

        after the board reboots go to the g-Code console and enter M122 and post this results here

        Hypercube-Evolution-Hybrid, Piezo Orion, Orbiter
        Duet WiFi 1.02 or later + DueX5
        RepRapFirmware for Duet 2 WiFi/Ethernet 3.4.0beta4 (2021-09-27 11:30:36)
        Duet WiFi Server: 1.26
        Duet Web Control 3.4.0beta4 (2021-09-27)

        1 Reply Last reply Reply Quote 0
        • ShOrTyundefined
          ShOrTy
          last edited by

          This is the report with 2.02 firmware:

          
          M122
          === Diagnostics ===
          RepRapFirmware for Duet 2 WiFi/Ethernet version 2.02(RTOS) running on Duet WiFi 1.02 or later
          Used output buffers: 3 of 20 (18 max)
          === RTOS ===
          Static ram: 25524
          Dynamic ram: 98640 of which 0 recycled
          Exception stack ram used: 512
          Never used ram: 6396
          Tasks: NETWORK(ready,544) HEAT(blocked,1232) MAIN(running,3780) IDLE(ready,200)
          Owned mutexes:
          === Platform ===
          Last reset 02:14:50 ago, cause: software
          Last software reset at 2020-01-06 16:36, reason: Watchdog timeout, spinning module GCodes, available RAM 6312 bytes (slot 1)
          Software reset code 0x4053 HFSR 0x00000000 CFSR 0x00000000 ICSR 0x0441f814 BFAR 0xe000ed38 SP 0x2000494c Task 0x4e49414d
          Stack: 004450eb 0042acdc 61000000 2000857c 200031d4 6f5523d2 a5a5a5a5 a5a5a5a5 a5a5a5a5 a5a5a5a5 0044bb0b 00000000 0044b913 00000008 0043943b 00000000 20009aa8 00000fff 6f5523d2 a5a5a5a5 0042acdd 20008570 20007a00
          Error status: 0
          Free file entries: 10
          SD card 0 detected, interface speed: 20.0MBytes/sec
          SD card longest block write time: 0.0ms, max retries 0
          MCU temperature: min 33.2, current 33.9, max 34.2
          Supply voltage: min 12.5, current 12.6, max 12.7, under voltage events: 0, over voltage events: 0, power good: yes
          Driver 0: standstill, SG min/max 0/181
          Driver 1: standstill, SG min/max 0/172
          Driver 2: standstill, SG min/max 83/329
          Driver 3: standstill, SG min/max not available
          Driver 4: standstill, SG min/max not available
          Date/time: 2020-01-06 18:51:32
          Cache data hit count 4294967295
          Slowest loop: 4.35ms; fastest: 0.08ms
          I2C nak errors 0, send timeouts 0, receive timeouts 0, finishTimeouts 0
          === Move ===
          Hiccups: 0, StepErrors: 0, LaErrors: 0, FreeDm: 240, MinFreeDm: 238, MaxWait: 3420424ms, Underruns: 0, 0
          Scheduled moves: 10, completed moves: 10
          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
          === 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 ===
          Slowest loop: 202.49ms; fastest: 0.08ms
          Responder states: HTTP(0) HTTP(0) HTTP(0) HTTP(0) FTP(0) Telnet(0) Telnet(0)
          HTTP sessions: 1 of 8
          - WiFi -
          Network state is running
          WiFi module is connected to access point
          Failed messages: pending 0, notready 0, noresp 1
          WiFi firmware version 1.23
          WiFi MAC address dc:4f:22:6e:6f:97
          WiFi Vcc 3.42, reset reason Turned on by main processor
          WiFi flash size 4194304, free heap 25824
          WiFi IP address 100.100.100.102
          WiFi signal strength -60dBm, reconnections 0, sleep mode modem
          Socket states: 0 0 0 0 0 0 0 0
          
          

          And this is the report with 2.05 firmware:

          M122
          === Diagnostics ===
          RepRapFirmware for Duet 2 WiFi/Ethernet version 2.05 running on Duet WiFi 1.02 or later
          Used output buffers: 1 of 24 (16 max)
          === RTOS ===
          Static ram: 25712
          Dynamic ram: 93184 of which 372 recycled
          Exception stack ram used: 272
          Never used ram: 11532
          Tasks: NETWORK(ready,752) HEAT(blocked,1232) MAIN(running,3736) IDLE(ready,160)
          Owned mutexes:
          === Platform ===
          Last reset 00:38:10 ago, cause: software
          Last software reset at 2020-01-09 17:26, reason: Assertion failed, spinning module Platform, available RAM 11212 bytes (slot 2)
          Software reset code 0x4090 HFSR 0x00000000 CFSR 0x00000000 ICSR 0x0441f000 BFAR 0xe000ed38 SP 0x20004b24 Task 0x4e49414d
          Stack: 000001a7 00462974 00445543 20002c54 0044d6d1 20002c54 00000000 00000000 ffffffff 20002c54 20003258 0026de28 8e471f13 00462424 a5a5a5a5 a5a5a5a5 0044d87f 20002c48 20004b80 00000000 0044be67 20002c20 004403e7
          Error status: 0
          Free file entries: 10
          SD card 0 detected, interface speed: 20.0MBytes/sec
          SD card longest block write time: 0.0ms, max retries 0
          MCU temperature: min 33.1, current 33.3, max 33.6
          Supply voltage: min 12.6, current 12.7, max 12.8, under voltage events: 0, over voltage events: 0, power good: yes
          Driver 0: standstill, SG min/max not available
          Driver 1: standstill, SG min/max not available
          Driver 2: standstill, SG min/max not available
          Driver 3: standstill, SG min/max not available
          Driver 4: standstill, SG min/max not available
          Date/time: 2020-01-09 18:04:11
          Cache data hit count 4294967295
          Slowest loop: 1.11ms; fastest: 0.07ms
          I2C nak errors 0, send timeouts 0, receive timeouts 0, finishTimeouts 0, resets 0
          === Move ===
          Hiccups: 0, FreeDm: 160, MinFreeDm: 160, MaxWait: 0ms
          Bed compensation in use: none, comp offset 0.000
          === DDARing ===
          Scheduled moves: 0, completed moves: 0, StepErrors: 0, LaErrors: 0, Underruns: 0, 0
          === Heat ===
          Bed heaters = 0 -1 -1 -1, chamberHeaters = -1 -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 ===
          Slowest loop: 200.63ms; fastest: 0.08ms
          Responder states: HTTP(0) HTTP(0) HTTP(0) HTTP(0) FTP(0) Telnet(0) Telnet(0)
          HTTP sessions: 1 of 8
          - WiFi -
          Network state is running
          WiFi module is connected to access point
          Failed messages: pending 0, notready 0, noresp 2
          WiFi firmware version 1.23
          WiFi MAC address 84:0d:8e:b3:b0:4d
          WiFi Vcc 3.39, reset reason Turned on by main processor
          WiFi flash size 4194304, free heap 22744
          WiFi IP address 100.100.100.102
          WiFi signal strength -59dBm, reconnections 0, sleep mode modem
          Socket states: 0 0 0 0 0 0 0 0
          
          1 Reply Last reply Reply Quote 0
          • SIamundefined
            SIam
            last edited by

            ok i think this is a topic for @dc42

            Hypercube-Evolution-Hybrid, Piezo Orion, Orbiter
            Duet WiFi 1.02 or later + DueX5
            RepRapFirmware for Duet 2 WiFi/Ethernet 3.4.0beta4 (2021-09-27 11:30:36)
            Duet WiFi Server: 1.26
            Duet Web Control 3.4.0beta4 (2021-09-27)

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