@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

@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

@t3p3tony Ok cool I will get one in the morning. Thanks for the help

@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.

@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

@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.

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

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

config.g

As the title suggests my duet 3 mini keeps randomly resetting during printing. it can happen anywhere from 1 hour to 8 hours into a job. The printer is a modified CR10 5s with Duet 3 mini, BLTouch and bondtech extruder.

Initially I suspected that it was due to a faulty power supply so I switched power supplies with another printer that has worked faultlessly. This did not solve the issue, the other printer continued to work whilst this printer continued to experience the same problem. Just to be sure I also replaced the wiring going to the power supply and deleted the power switch in case that was the issue.

My stepper drivers are running 1/16 microstepping and the printer is using a 0.8 nozzle so print speeds are low @30mm/s

Only thing I can think at the moment is it could be to do with the bed running through a SSR as per the original creality design.

Have included a copy of the M122 diagnostic file generated after the last incident. For some reason the wifi module is disabled after this reset. Usually it works but can be a bit temperamental. I just assumed it was down to the network at my place of work.

Would be incredibly grateful if someone could give me some advice as to what the issue could be. I really need to get this printer fixed fast as we have a few very large jobs that are running late due to this problem, although we have 4 printers this is one of the biggest and we need the build volume to finish the job. Other printers are running stock firmware and have no issues. Not sure if it is relevant but originally there was a problem with the board not running properly, I had organized a replacement but managed to fix it with a big old blast from an air gun connected to a compressor. the conclusion was that there must of been some debris from manufacture causing a short.

My printer at home also runs a Duet board and that has never had any problems.

SENT: M122
READ: === Diagnostics ===
READ: RepRapFirmware for Duet 3 Mini 5+ version 3.3 (2021-06-15 21:46:11) running on Duet 3 Mini5plus WiFi (standalone mode)
READ: Board ID: 95T1H-7396U-D65J0-40KMQ-L413Z-76AHS
READ: Used output buffers: 1 of 40 (1 max)
READ: === RTOS ===
READ: Static ram: 102724
READ: Dynamic ram: 106536 of which 0 recycled
READ: Never used RAM 34444, free system stack 159 words
READ: Tasks: NETWORK(ready,50.9%,372) HEAT(notifyWait,0.2%,366) Move(notifyWait,0.4%,338) CanReceiv(notifyWait,0.0%,941) CanSender(notifyWait,0.0%,371) CanClock(delaying,0.1%,340) TMC(notifyWait,4.5%,115) MAIN(running,38.4%,412) IDLE(ready,0.0%,29) AIN(delaying,5.6%,273), total 100.0%
READ: Owned mutexes: USB(MAIN)
READ: === Platform ===
READ: Last reset 07:27:49 ago, cause: reset button
READ: Last software reset time unknown, reason: HardFault invState, Platform spinning, available RAM 34444, slot 0
READ: Software reset code 0x4060 HFSR 0x40000000 CFSR 0x00020000 ICSR 0x0041e803 BFAR 0xe000ed38 SP 0x20011e48 Task TMC Freestk 125 ok
READ: Stack: 200190b0 20011bfc 20001064 e000e000 00000060 00089625 00000000 6100f000 e000e000 00089625 00000005 00000000 200117b0 0002cab3 00000004 00000004 200117b0 20011bf4 00000004 41008000 a5a5a5a5 0002cbdb a5a5a5a5 00087e75 a5a5a5a5 00000000 d9060105
READ: Error status: 0x00
READ: MCU revision 3, ADC conversions started 26869238, completed 26869238, timed out 0, errs 0
READ: Step timer max interval 744
READ: MCU temperature: min 19.4, current 22.8, max 25.4
READ: Supply voltage: min 14.0, current 14.2, max 14.2, under voltage events: 0, over voltage events: 0, power good: yes
READ: Heap OK, handles allocated/used 0/0, heap memory allocated/used/recyclable 0/0/0, gc cycles 0
READ: Driver 0: position 0, standstill, SG min/max 2/2, read errors 0, write errors 1, ifcnt 23, reads 37891, writes 9, timeouts 0, DMA errors 0
READ: Driver 1: position 0, standstill, SG min/max 0/0, read errors 0, write errors 1, ifcnt 23, reads 37891, writes 9, timeouts 0, DMA errors 0
READ: Driver 2: position 0, standstill, SG min/max 0/0, read errors 0, write errors 1, ifcnt 23, reads 37891, writes 9, timeouts 0, DMA errors 0
READ: Driver 3: position 0, standstill, SG min/max 2/2, read errors 0, write errors 1, ifcnt 23, reads 37890, writes 9, timeouts 0, DMA errors 0
READ: Driver 4: position 0, standstill, SG min/max 2/2, read errors 0, write errors 1, ifcnt 21, reads 37891, writes 9, timeouts 0, DMA errors 0
READ: Driver 5: position 0, assumed not present
READ: Driver 6: position 0, assumed not present
READ: Date/time: 1970-01-01 00:00:00
READ: Cache data hit count 4294967295
READ: Slowest loop: 6.95ms; fastest: 0.12ms
READ: === Storage ===
READ: Free file entries: 10
READ: SD card 0 detected, interface speed: 22.5MBytes/sec
READ: SD card longest read time 3.3ms, write time 0.0ms, max retries 0
READ: === Move ===
READ: DMs created 83, maxWait 0ms, bed compensation in use: none, comp offset 0.000
READ: === MainDDARing ===
READ: Scheduled moves 0, completed moves 0, hiccups 0, stepErrors 0, LaErrors 0, Underruns [0, 0, 0], CDDA state -1
READ: === AuxDDARing ===
READ: Scheduled moves 0, completed moves 0, hiccups 0, stepErrors 0, LaErrors 0, Underruns [0, 0, 0], CDDA state -1
READ: === Heat ===
READ: Bed heaters = 0 -1, chamberHeaters = -1 -1
READ: Heater 1 is on, I-accum = 0.0
READ: === GCodes ===
READ: Segments left: 0
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: USB is ready with "M122" in state(s) 0
READ: Aux is idle in state(s) 0
READ: Trigger is idle in state(s) 0
READ: Queue is idle in state(s) 0
READ: LCD is idle in state(s) 0
READ: SBC is idle in state(s) 0
READ: Daemon is idle in state(s) 0
READ: Aux2 is idle in state(s) 0
READ: Autopause is idle in state(s) 0
READ: Code queue is empty.
READ: === CAN ===
READ: Messages queued 241821, received 0, lost 0, longest wait 0ms for reply type 0, peak Tx sync delay 0, free buffers 17 (min 17), ts 134346/0/0
READ: Tx timeouts 0,0,134345,0,0,107474 last cancelled message type 30 dest 127
READ: 
READ: === Network ===
READ: Slowest loop: 199.87ms; fastest: 0.00ms
READ: Responder states: HTTP(0) HTTP(0) HTTP(0) HTTP(0) FTP(0) Telnet(0), 0 sessions
READ: HTTP sessions: 0 of 8
READ: - WiFi -
READ: Network state is disabled
READ: WiFi module is disabled
READ: Failed messages: pending 0, notready 0, noresp 2
READ: Socket states: 0 0 0 0 0 0 0 0
READ: ok

@oliof Someone might well have used both.

Creality are absolutely useless as far as any documentation goes, that’s why their printers are so cheap, copy someone else’s idea, sell it cheap and offer no support

I guess all I need to know is. If you had a BL-Touch and unplugged it and plugged a CR-Touch into the same cable would it work? In that case I can work backwards and probably figure it out.

Guessing that if I have it wired up correctly I just need to send a M401 command and the probe tip should pop out and if I issue M402 it goes back in again