Help please Duet 3 mini randomly resets during printing
-
Here is my config file, I am not an expert on setting these up but think that it seems ok.
; Configuration file for Duet 3 Mini 5+ (firmware version 3.3) ; executed by the firmware on start-up ; ; generated by RepRapFirmware Configuration Tool v3.3.2 on Mon Sep 06 2021 11:01:38 GMT+0100 (British Summer Time) ; General preferences G90 ; send absolute coordinates... M83 ; ...but relative extruder moves M550 P"CR10S5" ; set printer name ; Network M551 P"Milwyn" ; set password M552 S1 ; enable network M586 P0 S1 ; enable HTTP M586 P1 S0 ; disable FTP M586 P2 S0 ; disable Telnet ; Drives M569 P0.0 S0 ; physical drive 0.0 goes backwards M569 P0.1 S0 ; physical drive 0.1 goes backwards M569 P0.2 S0 ; physical drive 0.2 goes backwards M569 P0.4 S1 ; physical drive 0.4 goes forwards M584 X0.0 Y0.1 Z0.2:3 E0.4 ; set drive mapping M671 X-25:525 Y0:0 ; leadscrews at left (connected to Z) and right (connected to E1) of X axis M350 X16 Y16 Z16 E16 I1 ; configure microstepping with interpolation M92 X80.00 Y80.00 Z400.00 E415.00 ; set steps per mm M566 X900.00 Y900.00 Z60.00 E300.00 ; set maximum instantaneous speed changes (mm/min) M203 X6000.00 Y6000.00 Z180.00 E3600.00 ; set maximum speeds (mm/min) M201 X500.00 Y500.00 Z200.00 E500.00 ; set accelerations (mm/s^2) M906 X1300 Y1300 Z1000 E700 I30 ; set motor currents (mA) and motor idle factor in per cent M84 S30 ; Set idle timeout ; Axis Limits M208 X0 Y0 Z0 S1 ; set axis minima M208 X500 Y500 Z500 S0 ; set axis maxima ; Endstops M574 X1 S1 P"io5.in" ; configure active-high endstop for low end on X via pin io5.in M574 Y1 S1 P"io6.in" ; configure active-high endstop for low end on Y via pin io6.in M574 Z1 S2 ; configure Z-probe endstop for low end on Z ; Z-Probe M950 S0 C"io3.out" ; create servo pin 0 for BLTouch M558 P9 C"^io3.in" H5 F120 T6000 ; set Z probe type to bltouch and the dive height + speeds G31 P500 X-42 Y0 Z2 ; set Z probe trigger value, offset and trigger height M557 X75:425 Y75:425 S25 ; define mesh grid ; Heaters M308 S0 P"temp0" Y"thermistor" T100000 B3950 ; configure sensor 0 as thermistor on pin temp0 M950 H0 C"out2" Q10 T0 ; create bed heater output on out2 and map it to sensor 0 M307 H0 B0 S1.00 ; disable bang-bang mode for the bed heater and set PWM limit M140 H0 ; map heated bed to heater 0 M143 H0 S60 ; set temperature limit for heater 0 to 120C M308 S1 P"temp1" Y"thermistor" T100000 B3950 ; configure sensor 1 as thermistor on pin temp1 M950 H1 C"out1" T1 ; create nozzle heater output on out1 and map it to sensor 1 M307 H1 B0 S1.00 ; disable bang-bang mode for heater and set PWM limit M143 H1 S240 ; set temperature limit for heater 1 to 240C ; Fans M950 F0 C"out3" Q500 ; create fan 0 on pin out3 and set its frequency M106 P0 C"Part Cool" S0 H-1 ; set fan 0 name and value. Thermostatic control is turned off M950 F1 C"out4" Q500 ; create fan 1 on pin out4 and set its frequency M106 P1 C"Hotend" S1 H1:0 T45 ; set fan 1 name and value. Thermostatic control is turned on M950 F2 C"out5" Q500 ; create fan 2 on pin out5 and set its frequency M106 P2 C"Case1" S1 H1:0 T05 ; set fan 2 value. Thermostatic control is turned on M950 F3 C"out6" Q500 ; create fan 2 on pin out5 and set its frequency M106 P3 C"Case2" S1 H1:0 T05 ; set fan 2 value. Thermostatic control is turned on ; Tools M563 P0 S"Hotend" 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 ; Miscellaneous M501 ; load saved parameters from non-volatile memory M911 S10 R11 P"M913 X0 Y0 G91 M83 G1 Z3 E-5 F1000" ; set voltage thresholds and actions to run on power loss T0 ; select first tool -
This is M22 generated after printing for half hour, cannot see any obvious faults, there is a slight voltage drop but that is it.
M122 === Diagnostics === RepRapFirmware for Duet 3 Mini 5+ version 3.3 (2021-06-15 21:46:11) running on Duet 3 Mini5plus WiFi (standalone mode) Board ID: 95T1H-7396U-D65J0-40KMQ-L413Z-76AHS Used output buffers: 3 of 40 (26 max) === RTOS === Static ram: 102724 Dynamic ram: 106536 of which 0 recycled Never used RAM 31588, free system stack 120 words Tasks: NETWORK(ready,15.6%,226) HEAT(notifyWait,0.0%,366) Move(notifyWait,0.1%,292) CanReceiv(notifyWait,0.0%,941) CanSender(notifyWait,0.0%,357) CanClock(delaying,0.0%,340) TMC(notifyWait,0.7%,114) MAIN(running,82.8%,412) IDLE(ready,0.0%,29) AIN(delaying,0.8%,266), total 100.0% Owned mutexes: WiFi(NETWORK) === Platform === Last reset 01:40:30 ago, cause: software Last software reset at 2021-10-28 08:41, reason: User, GCodes spinning, available RAM 34444, slot 1 Software reset code 0x0003 HFSR 0x00000000 CFSR 0x00000000 ICSR 0x00000000 BFAR 0xe000ed38 SP 0x00000000 Task MAIN Freestk 0 n/a Error status: 0x00 MCU revision 3, ADC conversions started 6030451, completed 6030451, timed out 0, errs 0 Step timer max interval 1488 MCU temperature: min 21.9, current 25.2, max 25.4 Supply voltage: min 12.8, current 13.9, max 14.2, under voltage events: 0, over voltage events: 0, power good: yes Heap OK, handles allocated/used 99/1, heap memory allocated/used/recyclable 2048/14/0, gc cycles 0 Driver 0: position 9961, ok, SG min/max 0/118, read errors 0, write errors 0, ifcnt 21, reads 26584, writes 2, timeouts 0, DMA errors 0 Driver 1: position 15309, ok, SG min/max 0/92, read errors 0, write errors 0, ifcnt 21, reads 26584, writes 2, timeouts 0, DMA errors 0 Driver 2: position 1047, standstill, SG min/max 0/18, read errors 0, write errors 0, ifcnt 21, reads 26584, writes 2, timeouts 0, DMA errors 0 Driver 3: position 0, standstill, SG min/max 0/16, read errors 0, write errors 0, ifcnt 21, reads 26584, writes 2, timeouts 0, DMA errors 0 Driver 4: position 0, ok, SG min/max 0/34, read errors 0, write errors 0, ifcnt 21, reads 26584, writes 2, timeouts 0, DMA errors 0 Driver 5: position 0, assumed not present Driver 6: position 0, assumed not present Date/time: 2021-10-28 10:22:01 Cache data hit count 4294967295 Slowest loop: 375.89ms; fastest: 0.10ms === Storage === Free file entries: 9 SD card 0 detected, interface speed: 22.5MBytes/sec SD card longest read time 4.1ms, write time 208.5ms, max retries 0 === Move === DMs created 83, maxWait 3188961ms, bed compensation in use: mesh, comp offset 0.000 === MainDDARing === Scheduled moves 7524, completed moves 7513, hiccups 0, stepErrors 0, LaErrors 0, Underruns [0, 0, 0], CDDA state 3 === AuxDDARing === Scheduled moves 0, completed moves 0, hiccups 0, stepErrors 0, LaErrors 0, Underruns [0, 0, 0], CDDA state -1 === Heat === Bed heaters = 0 -1, chamberHeaters = -1 -1 Heater 0 is on, I-accum = 0.3 Heater 1 is on, I-accum = 0.8 === GCodes === Segments left: 1 Movement lock held by null HTTP is idle in state(s) 0 Telnet is idle in state(s) 0 File is doing "G1 X125.206 Y237.314 E48.3477" in state(s) 0 USB is idle in state(s) 0 Aux is idle in state(s) 0 Trigger is idle in state(s) 0 Queue is idle in state(s) 0 LCD is idle in state(s) 0 SBC is idle in state(s) 0 Daemon is idle in state(s) 0 Aux2 is idle in state(s) 0 Autopause is idle in state(s) 0 Code queue is empty. === CAN === Messages queued 26967, received 0, lost 0, longest wait 0ms for reply type 0, peak Tx sync delay 0, free buffers 17 (min 17), ts 14979/0/0 Tx timeouts 0,4,14979,0,0,11983 last cancelled message type 30 dest 127 === Network === Slowest loop: 658.01ms; fastest: 0.06ms Responder states: HTTP(0) HTTP(0) HTTP(0) HTTP(0) FTP(0) Telnet(0), 0 sessions HTTP sessions: 1 of 8 - WiFi - Network state is active WiFi module is connected to access point Failed messages: pending 0, notready 0, noresp 4 WiFi firmware version 1.26 WiFi MAC address d8:bf:c0:14:e7:e9 WiFi Vcc 3.40, reset reason Power up WiFi flash size 2097152, free heap 26072 WiFi IP address 192.168.4.103 WiFi signal strength -54dBm, mode 802.11n, reconnections 0, sleep mode modem Clock register 00002002 Socket states: 0 0 0 0 0 0 0 0 -
how is the board mounted and when did this start happening? How long had you used the board before it started?
Do you get the cause "reset button" on every time you get a reset? when you send M122?
READ: Last reset 07:27:49 ago, cause: reset button -
@mikenative and can you send a high res picture of the board. want to see if that air compressor blew off any tiny components.
-
@t3p3tony The board is mounted inside the original creality case on a 3D printed adapter.
It has a cooling fan either side to prevent overheating and nothing could touch the reset button as there are no moving parts.
Here is a picture. Normally there would be a power supply board in there below the duet but I have that externally for the moment whilst it is having problems.
-
@t3p3tony I will try and get a picture. Just testing the printer with a lower PWM speed for the bed SSR as that was the last thing on my list of possible issues that could be causing power supply problems. Will have to unplug everything to get to the board. I did examine it very carefully both before and after blasting it with air as I was specifically looking for anything that could possibly cause a short circuit. It looked like what it was, a brand new board
-
@mikenative are you by any chance printing multiple objects, with more than 20 on the build plate?
Duet WiFi hardware designer and firmware engineer
Please do not ask me for Duet support via PM or email, use the forum
http://www.escher3d.com, https://miscsolutions.wordpress.com -
@dc42 No just one big object at a time, usually around 1kg of filament per print.
I did read about a glitch that effected prints containing more than a certain number of objects, however the stuff we print is so big it has to get chopped up to even fit on the printer bed. The job I need the printer for is going to use around 35kg of filament and each section is roughly 300mm of square tube with 4.5mm wall thickness. Should be an easy job for the printer. You can see roughly what I mean in the picture. Prints are between 300mm-350mm tall. Excuse the sketchy glass bed, the bed on our other CR10-5s broke and I grabbed a random bit of toughened glass and stuck it on this printer as the touch probe can accommodate the difference in z height and the other printer has a fixed z endstop.
6FEC339A-5A27-4A2D-A928-0ADCCF4D9547.jpeg tall
When the printer is running it is absolutely perfect, basically silent and very smooth. Being a bed slinger with a massive bed and using a big nozzle to print heavy parts means I have the speeds turned right down.
-
@mikenative At this point i just need a picture in the area of the reset switch and SWD header specifically the components highlighted here:
-
@t3p3tony Ok cool
I will get one in the morning. Thanks for the help -
@t3p3tony I have solved it
Was kind of my fault. When I originally setup the printer it had no heated bed as a wire was broken. When I recommissioned the bed I activated it in the firmware but forgot all about setting a PWM frequency for the SSR. After experiencing the issue with the printer hanging up multiple times I went totally through the whole power supply chain and replaced everything with components I 100% knew to be working.
After this didn’t work I racked my brain and remembered there was a SSR being controlled with a PWM signal. As soon as I put in a frequency parameter of 10hz the issue went away. The printer has now completed 3 x 24 to 30 hour prints.
My guess is the default PWM frequency was causing the SSR to leak or feedback power which effected the reliability of the board and made it reset after a few hours. I am not an electronic engineer by any standard so this is just an assumption.
Thank you for your help. Hopefully if anyone else experiences a similar issue this information might come in handy and allow them to resolve the problem.
All the best
-
undefined Maurits referenced this topic
