what can "cause: reset button or watchdog"



  • I have bigbox printer with idex gonfiguration. I dont had any problem before this.

    Everything started yesterday. I had printing on going and suddenly u-axis titan extruder start skipping steps and i have to stop printing.

    Extruder bearing was jammed and i change it to new one. It work again.. i think.

    Today i start to print same print again. everything goes well until i noticed u-axis was skipped steps and print was fail.

    I start to printing again and after first layer Duet board reseting itself and print stopped. I try again and this time reseting happened on layer 6. Now i put voltage meter to measuring if power is going down and i start print again. Power is ok voltage is steady 24.25V but still duet reseting. It happend every print between 1 and 6 layers. I also try to print with X-axis and same thing happen. Any good idea what causing this?

    M122
    [CODE]
    === Diagnostics ===
    Used output buffers: 3 of 32 (16 max)
    === Platform ===
    RepRapFirmware for Duet WiFi version 1.20 running on Duet WiFi 1.0 + DueX5
    Board ID: 08DAM-999TL-MQ4S8-6JKFA-3SD6L-9P8RZ
    Static ram used: 15448
    Dynamic ram used: 99240
    Recycled dynamic ram: 4096
    Stack ram used: 1392 current, 6096 maximum
    Never used ram: 6192
    Last reset 00:52:41 ago, cause: reset button or watchdog
    Last software reset time unknown, reason: User, spinning module GCodes, available RAM 7896 bytes (slot 0)
    Software reset code 0x0003 HFSR 0x00000000, CFSR 0x00000000, ICSR 0x0441f000, BFAR 0xe000ed38, SP 0xffffffff
    Error status: 0
    Free file entries: 9
    SD card 0 detected, interface speed: 20.0MBytes/sec
    SD card longest block write time: 0.2ms
    MCU temperature: min 42.4, current 42.5, max 44.5
    Supply voltage: min 24.3, current 24.5, max 24.8, under voltage events: 0, over voltage events: 0
    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
    Expansion motor(s) stall indication: yes
    Date/time: 1970-01-01 00:00:00
    Cache data hit count 4294967295
    Slowest main loop (seconds): 0.063058; fastest: 0.000046
    === Move ===
    MaxReps: 0, StepErrors: 0, FreeDm: 240, MinFreeDm 240, MaxWait: 0ms, Underruns: 0, 0
    Scheduled moves: 0, completed moves: 0
    Bed compensation in use: mesh
    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: 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
    Failed messages: pending 0, notready 0, noresp 0
    WiFi firmware version 1.20
    WiFi MAC address 5c:cf:7f:2b:e7:3e
    WiFi Vcc 3.39, reset reason Turned on by main processor
    WiFi flash size 4194304, free heap 16656
    WiFi IP address 192.168.1.89
    WiFi signal strength -54dBm, 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)
    [/CODE]

    Logs not give anything

    power up + 00:00:00 Event logging started
    power up + 00:00:01 WiFi module started
    power up + 00:00:05 Wifi module is connected to access point ReiDiDin, IP address 192.168.1.89
    power up + 00:00:11 HTTP client 192.168.1.57 login succeeded
    2018-04-18 20:50:38 Date and time set at power up + 00:00:11
    2018-04-18 20:51:43 Started printing file 0:/gcodes/Sodastream_keg v7.gcode
    power up + 00:00:00 Event logging started
    power up + 00:00:00 WiFi module started
    power up + 00:00:05 Wifi module is connected to access point ReiDiDin, IP address 192.168.1.89


  • administrators

    1. Please upgrade to firmware 1.21.

    2. Please check that the edge of the Duet is not pressing against a back panel or anything else that could be activating the Reset button.

    3. If you are using a USB connection to the Duet, see https://duet3d.dozuki.com/Wiki/USB_ground_loops.



    1. Check
    2. Check
    3. No usb. Only wifi.

    Result

    Duet reseting print on layer 2 and also wifi going down. Now i cant connect it anymore with wifi.

    M122 i get it with usb

    READ: === Diagnostics ===
    READ: Used output buffers: 1 of 32 (11 max)
    READ: === Platform ===
    READ: RepRapFirmware for Duet 2 WiFi/Ethernet version 1.21 running on Duet WiFi 1.0 or 1.01 + DueX5
    READ: Board ID: 08DAM-999TL-MQ4S8-6JKFA-3SD6L-9P8RZ
    READ: Static ram used: 16152
    READ: Dynamic ram used: 100728
    READ: Recycled dynamic ram: 1904
    READ: Stack ram used: 3576 current, 4600 maximum
    READ: Never used ram: 7688
    READ: Last reset 00:14:24 ago, cause: reset button or watchdog
    READ: Last software reset time unknown, reason: User, spinning module GCodes, available RAM 7896 bytes (slot 0)
    READ: Software reset code 0x0003 HFSR 0x00000000, CFSR 0x00000000, ICSR 0x0441f000, BFAR 0xe000ed38, SP 0xffffffff
    READ: Error status: 0
    READ: Free file entries: 9
    READ: SD card 0 detected, interface speed: 20.0MBytes/sec
    READ: SD card longest block write time: 0.0ms
    READ: MCU temperature: min 44.5, current 44.7, max 45.2
    READ: Supply voltage: min 24.4, current 24.5, max 24.5, under voltage events: 0, over voltage events: 0
    READ: Driver 0: standstill, SG min/max not available
    READ: Driver 1: standstill, SG min/max not available
    READ: Driver 2: standstill, SG min/max not available
    READ: Driver 3: standstill, SG min/max not available
    READ: Driver 4: standstill, SG min/max not available
    READ: Driver 5: standstill, SG min/max not available
    READ: Driver 6: standstill, SG min/max not available
    READ: Driver 7: standstill, SG min/max not available
    READ: Driver 8: standstill, SG min/max not available
    READ: Driver 9: standstill, SG min/max not available
    READ: Expansion motor(s) stall indication: yes
    READ: Date/time: 1970-01-01 00:00:00
    READ: Slowest main loop (seconds): 0.165896; fastest: 0.000053
    READ: === Move ===
    READ: MaxReps: 0, StepErrors: 0, LaErrors: 0, FreeDm: 240, MinFreeDm 240, MaxWait: 0ms, Underruns: 0, 0
    READ: Scheduled moves: 0, completed moves: 0
    READ: Bed compensation in use: mesh
    READ: Bed probe heights: 0.000 0.000 0.000 0.000 0.000
    READ: === Heat ===
    READ: Bed heaters = 0 -1 -1 -1, chamberHeaters = -1 -1
    READ: Heater 1 is on, I-accum = 0.0
    READ: === GCodes ===
    READ: Segments left: 0
    READ: Stack records: 1 allocated, 0 in use
    READ: Movement lock held by null
    READ: http is idle in state(s) 0
    READ: telnet is idle in state(s) 0
    READ: file is idle in state(s) 0
    READ: serial is ready with "M122" in state(s) 0
    READ: aux is idle in state(s) 0
    READ: daemon is idle in state(s) 0
    READ: queue is idle in state(s) 0
    READ: autopause is idle in state(s) 0
    READ: Code queue is empty.
    READ: === Network ===
    READ: Responder states: HTTP(0) HTTP(0) HTTP(0) HTTP(0) FTP(0) Telnet(0) Telnet(0)
    READ: HTTP sessions: 0 of 8
    READ: - WiFi -
    READ: Network state is running
    READ: WiFi module is idle
    READ: Failed messages: pending 0, notready 0, noresp 0
    READ: WiFi firmware version 1.21
    READ: WiFi MAC address 5c:cf:7f:2b:e7:3e
    READ: WiFi Vcc 3.38, reset reason Turned on by main processor
    READ: WiFi flash size 4194304, free heap 19648
    READ: Socket states: 0 0 0 0 0 0 0 0
    READ: === Expansion ===
    READ: DueX I2C errors 0
    READ: ok
    SENT: M105
    READ: ok T:39.5 /0.0 31.8 /0.0 B:46.0 /0.0

    log

    power up + 00:00:00 Event logging started
    power up + 00:00:01 WiFi module started
    power up + 00:00:05 WiFi module is connected to access point ReiDiDin, IP address 192.168.1.89
    power up + 00:00:39 HTTP client 192.168.1.57 login succeeded
    2018-04-19 14:18:12 Date and time set at power up + 00:00:39
    2018-04-19 14:21:10 Started printing file 0:/gcodes/Sodastream_keg v7.gcode
    2018-04-19 14:27:34 Cancelled printing file 0:/gcodes/Sodastream_keg v7.gcode, print time was 0h 6m
    2018-04-19 14:41:38 Started printing file 0:/gcodes/Sodastream_keg v7.gcode
    power up + 00:00:00 Event logging started
    power up + 00:00:00 WiFi module started
    power up + 00:00:03 WiFi reported error: no known networks found
    power up + 00:00:03 WiFi module is idle
    power up + 00:16:48 Warning: VIN under-voltage event (8.6V)
    power up + 00:00:00 Event logging started
    power up + 00:00:01 WiFi module started
    power up + 00:00:05 WiFi module is connected to access point ReiDiDin, IP address 192.168.1.89
    power up + 00:00:36 HTTP client 192.168.1.57 login succeeded
    2018-04-19 15:07:34 Date and time set at power up + 00:00:36

    taking power off get wifi up again



  • Is a possible that u-axis stepper motor can couse this? I take that plug off and now print is going on layer 10.

    It skipping steps when this started and it never skip before. I drive it manually yesterday and it work well. Intresting....


  • administrators

    If disconnecting the U axis motor solved it, here are some possibilities:

    • Insufficient power to drive all the motors
    • Bad U axis driver - is it getting hot?
    • Short in U axis motor wiring


  • It look like it would work now.

    I have had this idex setup about 6month now and i am printed quite lot whitout problem. This print is printed only one material so only one (u or x) motor is used. Both axis have same kind and tall wiring. I check board with thermocraphy cameras after this print so we see how much those driver warm up.

    Maybe i could also try to place u-axis motor to another driver before i start to change that motor.


 

Looks like your connection to Duet3D was lost, please wait while we try to reconnect.