Duet Wifi resetting part way through prints



  • Hi, my Duet wifi started resetting part way through prints yesterday, I have not been able to get through a print since.

    I did a M122 and this is the result. Any help would be appreciated.

    4/26/2020, 2:27:44 PM: Connected to 192.168.1.137
    4/26/2020, 2:28:24 PM: M303 H1 P1 S250: Auto tuning heater 1 using target temperature 250.0°C and PWM 1.00 - do not leave printer unattended
    4/26/2020, 2:28:30 PM: : Auto tune phase 1, heater on
    4/26/2020, 2:30:15 PM: : Auto tune phase 2, heater off
    4/26/2020, 2:30:25 PM: : Auto tune phase 3, peak temperature was 262.9
    4/26/2020, 2:34:13 PM: : Warning: Heater 1 appears to be over-powered. If left on at full power, its temperature is predicted to reach 740C.
    Auto tune heater 1 completed in 349 sec
    Use M307 H1 to see the result, or M500 to save the result in config-override.g
    4/26/2020, 2:39:44 PM: Connection interrupted, attempting to reconnect...: HTTP request timed out
    4/26/2020, 2:39:46 PM: Connection established
    4/26/2020, 2:40:11 PM: M307 H1: Heater 1 model: gain 715.3, time constant 248.3, dead time 7.8, max PWM 1.00, calibration voltage 12.2, mode PID, inverted no, frequency default
    Computed PID parameters for setpoint change: P8.0, I0.182, D43.4
    Computed PID parameters for load change: P8.0,
    4/26/2020, 2:47:09 PM: Connection interrupted, attempting to reconnect...: HTTP request timed out
    4/26/2020, 2:47:11 PM: Connection established
    4/26/2020, 2:48:40 PM: : Warning: No M501 command was executed in config.g
    4/26/2020, 2:52:48 PM: : Error: Z probe was not triggered during probing move
    4/26/2020, 2:53:32 PM: Connection interrupted, attempting to reconnect...: HTTP request timed out
    4/26/2020, 2:56:08 PM: Connection established
    4/26/2020, 2:56:10 PM: Connection interrupted, attempting to reconnect...: Network error
    4/26/2020, 2:56:11 PM: Connection established
    4/26/2020, 2:57:46 PM: M32 "0:/gcodes/aqua_tube_holder.gcode": File 0:/gcodes/aqua_tube_holder.gcode selected for printing
    4/26/2020, 3:28:21 PM: Connection interrupted, attempting to reconnect...: HTTP request timed out
    4/26/2020, 3:28:22 PM: Connection established
    4/26/2020, 3:31:38 PM: M122: === Diagnostics ===
    RepRapFirmware for Duet 2 WiFi/Ethernet version 2.05.1 running on Duet WiFi 1.02 or later
    Board ID: 08DGM-9568A-F23SD-6J9DL-3SN6K-KTRZH
    Used output buffers: 3 of 24 (19 max)
    === RTOS ===
    Static ram: 25712
    Dynamic ram: 93140 of which 0 recycled
    Exception stack ram used: 320
    Never used ram: 11900
    Tasks: NETWORK(ready,572) HEAT(blocked,1232) MAIN(running,3816) IDLE(ready,160)
    Owned mutexes:
    === Platform ===
    Last reset 00:17:36 ago, cause: power up
    Last software reset at 2020-04-26 14:47, reason: User, spinning module GCodes, available RAM 11380 bytes (slot 3)
    Software reset code 0x0003 HFSR 0x00000000 CFSR 0x00000000 ICSR 0x0441f000 BFAR 0xe000ed38 SP 0xffffffff Task 0x4e49414d
    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 28.4, current 28.6, max 30.8
    Supply voltage: min 12.1, current 12.2, max 12.3, 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-04-26 15:31:37
    Cache data hit count 3242144632
    Slowest loop: 6.98ms; fastest: 0.06ms
    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: 78.29ms; fastest: 0.00ms
    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 0
    WiFi firmware version 1.21
    WiFi MAC address 2c:3a:e8:0b:02:f1
    WiFi Vcc 3.42, reset reason Turned on by main processor
    WiFi flash size 4194304, free heap 14232
    WiFi IP address 192.168.1.137
    WiFi signal strength -63dBm, reconnections 0, sleep mode modem
    Socket states: 0 0 0 0 0 0 0 0
    

  • Moderator

    Power supply?



  • @Phaedrux said in Duet Wifi resetting part way through prints:

    Power supply?

    Are you asking what is my power supply or are you asking if my power supply is the problem?


  • Moderator

    Both.

    Last reset 00:17:36 ago, cause: power up

    If this M122 was immediately after the reset the reset reason is power.

    Are your VIN terminal screws tight?



  • Yes, the M122 was the next thing I did after I noticed print stopped.

    Its just a cheap unbranded 12v psu, all my connections are good, so you would say the PSU need to be replaced?


  • Moderator

    Without further details indicating something else that would probably be my first focus.



  • Ok, so just to be sure, the M122 did not indicate a problem with the duet board itself? But it indicated an issue with the power supply? I just want to make sure there is nothing wrong with the duet board itself.


  • Moderator

    From my limited knowledge, All it indicated was that the last time it rebooted was because power was removed and applied again, like a normal power off and on.

    @dc42 would have a much better idea if there is something else in there.

    So for now wait and see if anyone else has any ideas. Give your printer a once over and see if you can identify anything amiss.

    Getting a quality power supply as a replacement wouldn't be the worst thing in the world as a precaution.



  • I have a corsair 800 watt atx that I hooked up, about to start another print, ill let ya know if it resets again.



  • It happened again after I switched the PSU. Here is the latest M122

    4/26/2020, 5:04:28 PM: m122: === Diagnostics ===
    RepRapFirmware for Duet 2 WiFi/Ethernet version 2.05.1 running on Duet WiFi 1.02 or later
    Board ID: 08DGM-9568A-F23SD-6J9DL-3SN6K-KTRZH
    Used output buffers: 3 of 24 (20 max)
    === RTOS ===
    Static ram: 25712
    Dynamic ram: 93140 of which 0 recycled
    Exception stack ram used: 320
    Never used ram: 11900
    Tasks: NETWORK(ready,572) HEAT(blocked,1232) MAIN(running,3800) IDLE(ready,160)
    Owned mutexes: WiFi(NETWORK)
    === Platform ===
    Last reset 00:01:59 ago, cause: power up
    Last software reset at 2020-04-26 14:47, reason: User, spinning module GCodes, available RAM 11380 bytes (slot 3)
    Software reset code 0x0003 HFSR 0x00000000 CFSR 0x00000000 ICSR 0x0441f000 BFAR 0xe000ed38 SP 0xffffffff Task 0x4e49414d
    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 29.8, current 29.9, max 30.9
    Supply voltage: min 12.1, current 12.2, max 12.3, 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-04-26 17:04:27
    Cache data hit count 352585371
    Slowest loop: 7.03ms; fastest: 0.06ms
    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: 78.60ms; fastest: 0.00ms
    Responder states: HTTP(0) HTTP(0) HTTP(0) HTTP(0) FTP(0) Telnet(0) Telnet(0)
    HTTP sessions: 2 of 8
    - WiFi -
    Network state is running
    WiFi module is connected to access point 
    Failed messages: pending 0, notready 0, noresp 0
    WiFi firmware version 1.21
    WiFi MAC address 2c:3a:e8:0b:02:f1
    WiFi Vcc 3.42, reset reason Turned on by main processor
    WiFi flash size 4194304, free heap 14584
    WiFi IP address 192.168.1.137
    WiFi signal strength -64dBm, reconnections 0, sleep mode modem
    Socket states: 0 0 0 0 0 0 0 0
    
    

  • Moderator

    Can you start another print and gather another M122 after it's been printing for a few minutes?

    Also post your config.g



  • Ok here is the m122 a few minutes after the print started.

    4/26/2020, 6:06:24 PM	M122
    === Diagnostics ===
    RepRapFirmware for Duet 2 WiFi/Ethernet version 2.05.1 running on Duet WiFi 1.02 or later
    Board ID: 08DGM-9568A-F23SD-6J9DL-3SN6K-KTRZH
    Used output buffers: 3 of 24 (19 max)
    === RTOS ===
    Static ram: 25712
    Dynamic ram: 93176 of which 0 recycled
    Exception stack ram used: 440
    Never used ram: 11744
    Tasks: NETWORK(ready,628) HEAT(blocked,1232) MAIN(running,3736) IDLE(ready,160)
    Owned mutexes: WiFi(NETWORK)
    === Platform ===
    Last reset 00:09:40 ago, cause: power up
    Last software reset at 2020-04-26 17:24, reason: User, spinning module GCodes, available RAM 11900 bytes (slot 0)
    Software reset code 0x0003 HFSR 0x00000000 CFSR 0x00000000 ICSR 0x0441f000 BFAR 0xe000ed38 SP 0xffffffff Task 0x4e49414d
    Error status: 0
    Free file entries: 9
    SD card 0 detected, interface speed: 20.0MBytes/sec
    SD card longest block write time: 0.0ms, max retries 0
    MCU temperature: min 28.0, current 28.6, max 29.0
    Supply voltage: min 12.0, current 12.1, max 12.3, under voltage events: 0, over voltage events: 0, power good: yes
    Driver 0: standstill, SG min/max 0/467
    Driver 1: standstill, SG min/max 0/360
    Driver 2: ok, SG min/max not available
    Driver 3: standstill, SG min/max 0/1023
    Driver 4: standstill, SG min/max not available
    Date/time: 2020-04-26 18:06:24
    Cache data hit count 1730644159
    Slowest loop: 2.33ms; fastest: 0.07ms
    I2C nak errors 0, send timeouts 0, receive timeouts 0, finishTimeouts 0, resets 0
    === Move ===
    Hiccups: 0, FreeDm: 159, MinFreeDm: 128, MaxWait: 0ms
    Bed compensation in use: mesh, comp offset 0.000
    === DDARing ===
    Scheduled moves: 1930, completed moves: 1890, StepErrors: 0, LaErrors: 0, Underruns: 0, 1
    === Heat ===
    Bed heaters = 0 -1 -1 -1, chamberHeaters = -1 -1
    Heater 0 is on, I-accum = 0.0
    Heater 1 is on, I-accum = 0.4
    === GCodes ===
    Segments left: 1
    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 doing "G1 X-14.396 Y-7.509 E1.7842" in state(s) 0
    serial is idle in state(s) 0
    aux is ready with "M408 S1" 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: 175.22ms; fastest: 0.08ms
    Responder states: HTTP(0) HTTP(0) HTTP(0) HTTP(0) FTP(0) Telnet(0) Telnet(0)
    HTTP sessions: 2 of 8
    - WiFi -
    Network state is running
    WiFi module is connected to access point 
    Failed messages: pending 0, notready 0, noresp 0
    WiFi firmware version 1.21
    WiFi MAC address 2c:3a:e8:0b:02:f1
    WiFi Vcc 3.42, reset reason Turned on by main processor
    WiFi flash size 4194304, free heap 14824
    WiFi IP address 192.168.1.137
    WiFi signal strength -68dBm, reconnections 0, sleep mode modem
    Socket states: 0 0 0 0 0 0 0 0
    


  • here is my config file

    ; Configuration file for Duet WiFi (firmware version 2.03)
    ; executed by the firmware on start-up
    ;
    ; generated by RepRapFirmware Configuration Tool v2.1.8 on Wed Apr 01 2020 17:56:19 GMT-0500 (Central Daylight Time)
    
    ; General preferences
    G90                                      ; send absolute coordinates...
    M83                                      ; ...but relative extruder moves
    M550 P"FT5"                              ; set printer name
    
    ; Network
    M552 S1                                  ; enable network
    M586 P0 S1                               ; enable HTTP
    M586 P1 S0                               ; disable FTP
    M586 P2 S0                               ; disable Telnet
    
    ; Drives
    M569 P0 S0                               ; physical drive 0 goes forwards
    M569 P1 S0                               ; physical drive 1 goes forwards
    M569 P2 S0                               ; physical drive 2 goes forwards
    M569 P3 S1                               ; physical drive 3 goes forwards
    M584 X0 Y1 Z2 E3                         ; set drive mapping
    M350 X16 Y16 Z16 E16 I1                  ; configure microstepping with interpolation
    M92 X80.00 Y80.00 Z400.00 E837      ; set steps per mm
    M566 X900.00 Y900.00 Z12.00 E1500.00     ; set maximum instantaneous speed changes (mm/min)
    M203 X6000.00 Y6000.00 Z180.00 E1200.00  ; set maximum speeds (mm/min)
    M201 X1000.00 Y1000.00 Z20.00 E3000      ; set accelerations (mm/s^2)
    M906 X1500 Y1500 Z2000 E1400 I30         ; set motor currents (mA) and motor idle factor in per cent
    M84 S30                                  ; Set idle timeout
    
    ; Axis Limits
    ;M208 X0 Y-10 Z0 S0                      ; set axis minima
    ;M208 X300 Y300 Z400 S0                  ; set axis maxima
    M208 X-150:150 Y-150:150                 ; set axis limits
    ; Endstops
    M574 X1 Y1 S0                            ; set active low and disabled endstops
    M574 Z1 S2                               ; set endstops controlled by probe
    
    ; Z-Probe
    M307 H3 A-1 C-1 D-1                          ; disable heater on PWM channel for BLTouch
    M558 P9 H5 F120 T6000                        ; set Z probe type to bltouch and the dive height + speeds
    G31 P25 X48 Y-5 Z4                           ; set Z probe trigger value, offset and trigger height
    M557 X-145:145 Y-145:145 S30                 ; define mesh grid
    
    ; Heaters
    M305 P0 T100000 B4138 R4700              ; set thermistor + ADC parameters for heater 0
    M143 H0 S120                             ; set temperature limit for heater 0 to 120C
    M305 P1 T100000 B4725 C7.060000e-8 R4700 ; set thermistor + ADC parameters for heater 1
    M143 H1 S280                             ; set temperature limit for heater 1 to 280C
    M307 H1 A715.3, C248.3, D7.8 S1          ; PID for hotend
    ; Fans
    M106 P0 S0 I0 F500 H-1                   ; set fan 0 value, PWM signal inversion and frequency. Thermostatic control is turned off
    M106 P1 S1 I0 F500 H1 T45                ; set fan 1 value, PWM signal inversion and frequency. Thermostatic control is turned on
    
    ; Tools
    M563 P0 D0 H1 F0                         ; define tool 0
    G10 P0 X0 Y0 Z0                          ; set tool 0 axis offsets
    G10 P0 R0 S0                             ; set initial tool 0 active and standby temperatures to 0C
    
    ; Custom settings are not defined
    
    
    


  • Here is the m122 after that print failled

    4/26/2020, 6:18:37 PM	m122
    === Diagnostics ===
    RepRapFirmware for Duet 2 WiFi/Ethernet version 2.05.1 running on Duet WiFi 1.02 or later
    Board ID: 08DGM-9568A-F23SD-6J9DL-3SN6K-KTRZH
    Used output buffers: 1 of 24 (19 max)
    === RTOS ===
    Static ram: 25712
    Dynamic ram: 93140 of which 0 recycled
    Exception stack ram used: 320
    Never used ram: 11900
    Tasks: NETWORK(ready,628) HEAT(blocked,1232) MAIN(running,3760) IDLE(ready,160)
    Owned mutexes:
    === Platform ===
    Last reset 00:06:38 ago, cause: power up
    Last software reset at 2020-04-26 17:24, reason: User, spinning module GCodes, available RAM 11900 bytes (slot 0)
    Software reset code 0x0003 HFSR 0x00000000 CFSR 0x00000000 ICSR 0x0441f000 BFAR 0xe000ed38 SP 0xffffffff Task 0x4e49414d
    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 27.6, current 27.8, max 29.5
    Supply voltage: min 12.1, current 12.2, max 12.3, 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-04-26 18:18:36
    Cache data hit count 1214738893
    Slowest loop: 2.43ms; fastest: 0.06ms
    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: 51.93ms; fastest: 0.00ms
    Responder states: HTTP(0) HTTP(0) HTTP(0) HTTP(0) FTP(0) Telnet(0) Telnet(0)
    HTTP sessions: 2 of 8
    - WiFi -
    Network state is running
    WiFi module is connected to access point 
    Failed messages: pending 0, notready 0, noresp 0
    WiFi firmware version 1.21
    WiFi MAC address 2c:3a:e8:0b:02:f1
    WiFi Vcc 3.42, reset reason Turned on by main processor
    WiFi flash size 4194304, free heap 14504
    WiFi IP address 192.168.1.137
    WiFi signal strength -68dBm, reconnections 0, sleep mode modem
    Socket states: 0 0 0 0 0 0 0 0
    


  • This started after I put on a water cooled hotend, the E3d Titan Aqua, the only thing I can think of is, now there is no hotend fan hooked to the duet board, the water cooling pump and rad/fan are powered directly by the PSU. I don't know if the issue is a coincidence or is the duet resetting because its not sinsing a hotend fan being hooked up?

    other then that, nothing has changed, I used the same heater, same thermistor, heater block, motor that was already there from the regular e3d titan.


  • Moderator

    I don't think so. If the pump is directly connected to the PSU and there is no duet control over the pump you can remove the M106 P1 entry entirely from config.g since there is no fan connected.

    Did you PID tune the heater again after changing over? Not that that would cause this.

    Did anything else get changed?

    Is the pump drawing a lot of amps or something?



  • Yes I did do a re-tune on the hotend. I did consider the pump might be causing the resets, but after switching the board over the the 800watt atx psu and leaving the rest hooked up to the old PSU, it still is resetting.



  • Everytime it resets, I get this massage on the counsole.

    https://drive.google.com/file/d/1baVuvLro9hD_JT6FbqInWpsegVn8Mlew/view?usp=drivesdk


  • Moderator

    That heater warning is to let you know how hot your heater could get in a closed circuit failure.



  • I don't even know if reset is the right term, because after the printer stops, the progress bar shows 100% like the print completed

    The printer just stops in mid movement and the layer fan shuts off.


  • Moderator

    But you get that heater and wifi message on the PanelDue? Those messages come at startup as config.g is read, so it does sound like it is resetting.



  • Yes, that message comes up on the PanelDue



  • Well, I never figured out what the issue is, but its something with the board itself, I changed it with another duet I have on a different printer and no problems now.



  • Supprised, figured I'd get a little more help on this then I did....


  • Moderator

    Was there possibly anything shorting against the board that is now moved with the new board?

    Can you post some photos of the board? Close up and well lit. Maybe we can spot a damaged component.

    Is the board new?


Log in to reply