Duet Wifi resetting part way through prints
-
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.
-
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
-
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.
-
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....
-
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?
-
No, nothing shorting against the board, it was mounted on 20mm printed stand offs, then I put nylon washers between the board and the screws. So its, screw, nylon washer, board, 20mm 3d printed standoff, mounted to a melamine board.
Bought the board in 2018, but sadly, It was for a project that I had set aside and didn't get back to till about 3 weeks ago, so the board had probally been used less then 50 times total.
https://drive.google.com/file/d/1bjw1bgBfpSLfJ_P6Pq1asx-cXwlaMBEv/view?usp=drivesdk
https://drive.google.com/file/d/1bjptjoMHgpWTFbWczqt_GfarV0bqMLCg/view?usp=drivesdk
-
The google drive links are private. I can't access it.
-
Try it now
-
@Bmilam I can't see anything obvious from the pictures. The only odd thing is that some of the text on the top of the main processor is missing. This could have come off if there was a sticker on it that you took off (and then cleaned with acetone or similar), but may be a sign that the processor has overheated, and may be causing the failures.
M122 still doesn't show anything amiss, other than the board was recently powered on. Swapping the boards isn't conclusive; are you using the same SD card, same firmware version and running the same gcode file? Redoing the wiring may also have removed the issue. If you reformatted and rebuilt the SD card, that may have resolved the issue. You're changing too many parameters to know exactly where the problem is. If you want to find out the exact problem, you'll need to connect the old board and do more troubleshooting.
Bought the board in 2018
Unfortunately, warranty is for 6 months. See https://www.duet3d.com/warranty
Supprised, figured I'd get a little more help on this then I did....
@Phaedrux has been as helpful as he can. You didn't supply much information up front. The M122 responses don't indicate anything, other than the power is turning off. All we can do is offer advice to try and track down where the problem is; we're not in the room with you, and we don't know what's causing the fault either, based on what you're telling us. It's not the sort of fault that happens every day, so requires investigation to answer.
Ian
-
@Bmilam said in Duet Wifi resetting part way through prints:
Last reset 00:17:36 ago, cause: power up
That bit (which is in all your M122 reports) indicates that the Duet reset because there was no power to the microcontroller. Possible reasons include:
- PSU problem. Note, most 12v ATX PSUs need a dummy load on the 5V rail to prevent them form getting over-voltage on the 12V rail and resetting.
- VIN terminal block screws on the Duet not tight
- Something is shorting out or overloading the 5V or 3.3V rail of the Duet. A common cause is endstop switches that are connected to the wrong pins of the endstop connector.
-
undefined Inlinebrother referenced this topic
