1. Home
  2. Categories
  3. Duet Hardware and wiring
  4. Duet Resetting

Duet Resetting

  • kazolar

    Something changed, I had some physical crash, and I'm trying to figure out what wiring got disrupted.

    I am getting a reset

    Last reset 00:04:53 ago, cause: software
    Last software reset at 2019-12-01 22:51, reason: Stuck in spin loop, spinning module GCodes, available RAM 7708 bytes (slot 2)
    Software reset code 0x4043 HFSR 0x00000000 CFSR 0x00000000 ICSR 0x0041f80f BFAR 0xe000ed38 SP 0x2000322c Task 0x454c4449
    Stack: 00449d75 0044a0d2 61000000 a5a5a5a5 00449d75 a5a5a5a5 a5a5a5a5 20003250 200030f8 200048d4 0000b483 200062f4 20001778 20003250 200062ec 00000004 200030d0 2000178c 20003250 200030c8 00000001 200032a8 4e49414d

    Got another one.
    Getting very confusing.
    Last software reset time unknown, reason: Assertion failed, spinning module Platform, available RAM 31760 bytes (slot 2)
    Software reset code 0x4090 HFSR 0x00000000 CFSR 0x00000000 ICSR 0x0440f819 BFAR 0xe000ed38 SP 0x2001ff8c Task 0x454c4449
    Stack: 000002f3 00462da8 0044a089 20002be0 0044afe5 00000011 00020000 20005564 00000001 10000000 0043811f 2000628c 00000000 20006228 004462b3 00000000 20006290 2000628c 20006300 20006228 fffffffd 00000000 00f00000

    Any suggestions would be helpful

    EDIT:

    A wire got stuck in the fan.
    Things were overheating -- my best guess.
    No temp errors though.
    Cleared up resets gone

    0
  • dc42
    administrators

    @kazolar, which Duet, and which firmware version?

    0
  • kazolar

    @dc42 duet 2 2.03RC2. I've never had this happen, I sorta expected a temp error -- as soon as all steppers (duet and duex5) were active about 30 seconds later it would reset -- everything is in a case, but I've been tweaking a few peripheral wires, and one nylon sleeved wire got into the fan for the duet/duex5, so it had no airflow.

    0 dc42 1 Reply
  • Veti

    @kazolar said in Duet Resetting:

    0x4090

    do you have a usb cable connected?

    0
  • dc42
    administrators

    @kazolar said in Duet Resetting:

    @dc42 duet 2 2.03RC2. I've never had this happen, I sorta expected a temp error -- as soon as all steppers (duet and duex5) were active about 30 seconds later it would reset -- everything is in a case, but I've been tweaking a few peripheral wires, and one nylon sleeved wire got into the fan for the duet/duex5, so it had no airflow.

    Can you reproduce this issue with firmware 2.04? Another users has also reported a reset when I would have expected an over-temperature warning from one of the drivers.

    0
  • kazolar

    @dc42 I'll update to 2.04 later this week (I have some customizations I've applied to the firmware) -- so I need to move my diffs over. I commented out behavior to comeback to Z after toolchange, a few other tweaks. I'm not sure I would purposely disconnect the fan, but I'll try it. @Veti no, I don't use a usb cable.

    0 dc42 1 Reply
  • dc42
    administrators

    @kazolar said in Duet Resetting:

    @dc42 I'll update to 2.04 later this week (I have some customizations I've applied to the firmware) -- so I need to move my diffs over. I commented out behavior to comeback to Z after toolchange, a few other tweaks. I'm not sure I would purposely disconnect the fan, but I'll try it. @Veti no, I don't use a usb cable.

    Please use 2.05RC2 if I have released it by then.

    0
  • kazolar

    @dc42 had a reset with most recent 2.05
    Happened during homing of the gantry axes. Seems this started happening when I started using

    M42 P7 S255 and G4 as part of the homing routine

    Here is my home gantry -- I need to use the G4 commands to make sure the homing switches which M42 command toggle are enabled correctly.

    M42 P7 S255
    G4 S1
    G91
    G1 V700 W700 A-700 Y-700 U700 X-700 F2500 S1
    G1 Y3 U-3 X3 V-3 W-3 A3 F300 S2
    G1 Y-20 U20 X-20 V20 W20 A-20 F50 S1
    M579 U1
    G90
    G4 S3
    M42 P7 S0

    === Diagnostics ===
    RepRapFirmware for Duet 2 WiFi/Ethernet version 2.05 running on Duet Ethernet 1.02 or later + DueX5
    Board ID: 08DGM-9T6BU-FG3S0-7JTD4-3S06K-1A4ZD
    Used output buffers: 3 of 24 (10 max)
    === RTOS ===
    Static ram: 25708
    Dynamic ram: 96296 of which 0 recycled
    Exception stack ram used: 320
    Never used ram: 8748
    Tasks: NETWORK(ready,748) HEAT(blocked,1236) DUEX(suspended,168) MAIN(running,3756) IDLE(ready,156)
    Owned mutexes:
    === Platform ===
    Last reset 00:00:27 ago, cause: software
    Last software reset at 2019-12-22 23:37, reason: Stuck in spin loop, spinning module GCodes, available RAM 8372 bytes (slot 3)
    Software reset code 0x4043 HFSR 0x00000000 CFSR 0x00000000 ICSR 0x0041f80f BFAR 0xe000ed38 SP 0x2000323c Task 0x454c4449
    Stack: 00445ac9 00444abc 61000000 a5a5a5a5 00445ac9 a5a5a5a5 a5a5a5a5 20003264 20003104 00000002 200048ec 02c344a8 20001780 20004cf4 20003264 20004cec 00000004 20001794 200030dc 20003264 200030d4 00000001 200032bc
    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 23.3, current 23.9, max 24.0
    Supply voltage: min 24.7, current 24.7, max 24.9, 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
    Driver 5: standstill, SG min/max not available
    Driver 6: standstill, SG min/max not available
    Driver 7: standstill, SG min/max not available
    Driver 8: standstill, SG min/max not available
    Driver 9: standstill, SG min/max not available
    Date/time: 2019-12-22 23:38:17
    Cache data hit count 52619560
    Slowest loop: 8.09ms; 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
    Heater 1 is on, I-accum = 0.0
    === 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: 6.76ms; fastest: 0.02ms
    Responder states: HTTP(0) HTTP(0) HTTP(0) HTTP(0) FTP(0) Telnet(0) Telnet(0)
    HTTP sessions: 1 of 8
    Interface state 5, link 100Mbps full duplex

    0
Log in to reply
 
Unless otherwise noted, all forum content is licensed under CC-BY-SA