Duet 2 Wifi Random Resets
-
@mrawesome987 get an output of M122 after the reset has occurred and post it here
-
Also include your full config.g please.
When and where did you purchase your Duet?
Have you verified that the power supply is outputting a steady voltage with a multimeter?
Check also that the VIN terminals are screws down tightly and make sure you're using boot lace ferrules.
-
@phaedrux here is my current config:
; Prologue and comms section M111 S0 ; Debug off M550 CoreXY ; Machine name (can be anything you like) M551 Preprap ; Machine password ;*** If you have more than one Duet on your network, they must all have different MAC addresses, so change the last digits ;M540 P0xBE:0xEF:0xDE:0xAD:0xFE:0xED ; MAC Address M552 S1 ;*** Adjust the IP address and gateway in the following 2 lines to suit your network M552 P192.168.1.82 ; IP address (0 = use DHCP) M554 P192.168.1.1 ; Gateway M553 P255.255.255.0 ; Netmask M555 P2 ; Set output to look like Marlin M575 P1 B57600 S1 ; Comms parameters for PanelDue ; Movement section M669 K1 ; switch to CoreXY mode M569 P0 S0 ; X motor runs forwards M569 P1 S0 ; Y motor runs forwards M569 P2 S0 ; Drive 2 goes forwards M569 P3 S1 ; Drive 3 goes forwards ;M569 P4 S1 ; Drive 4 goes forwards M584 X0 Y1 Z2 E3 M574 X1 S1 P"xstop" ; X min active high endstop switch M574 Y2 S1 P"ystop" ; Y min active high endstop switch M906 X1800 Y1800 Z1800 E1100 ; Set motor currents (mA) M201 X1200 Y1200 Z100 E10000 ; Accelerations (mm/s^2) M203 X6000 Y6000 Z400 E6000 ; Maximum speeds (mm/min) M566 X600 Y600 Z600 E3000 ; Minimum speeds mm/minute M208 X260 Y270 Z340 ; set axis maxima (adjust to suit your machine) M208 X0 Y0 Z-0.2 S1 ; set axis minimum (adjust to make X=0 and Y=0 the edge of the bed) M92 X80 Y80 Z400 ; Set axis steps/mm M92 E400 ; Set extruder steps per mm G21 ; Work in millimetres G90 ; Send absolute coordinates... M83 ; ...but relative extruder moves ; Z probe section M307 H3 A-1 C-1 D-1 M558 P9 C"^zprobe.in" H5 F100 T2000 M950 S0 C"exp.heater3" G31 X0 Y-35 Z2.8 P25 ; Heater and thermistor section ;*** If you have a Duet board with 1K thermistor series resistors, change R4700 to R1000 to the following M308 commands M308 S0 P"bed_temp" Y"thermistor" T100000 B3950 ; define bed temperature sensor M308 S1 P"e0_temp" Y"thermistor" T100000 B4725 C7.06e-8 ; define E0 temperature sensor M950 H0 C"bed_heat" T0 ; heater 0 uses the bed_heat pin, sensor 0 M950 H1 C"e0_heat" T1 ; heater 1 uses the e0_heat pin and sensor 1 M140 H0 M307 H1 A4190.5 C189.9 D2.4 V24.0 B0 ;M301 H1 P10 I0.10 D100 T0.50 S1.0 ; PID settings for extruder 0 M570 S12000 ; Increase to allow extra heating time if needed ;Fan M950 F0 C"fan0" ;Create Fan 0 M106 P0 S0 H-1 M950 F1 C"fan1" ;Create Fan 1 M106 P1 S1 H-1 ; Tool definition section M563 P0 D0 H1 F0 ; Define tool 0 to use extruder drive 0 and heater 1 G10 P0 R0 S0 ; Set tool 0 operating and standby temperatures ; Bed probe section (not needed if you use a bed.g file) ;*** Adjust the XY coordinates in the following M557 commands to suit your build and the position of your Z probe ;M557 P0 X60 Y0 ; Four... ;M557 P1 X60 Y165 ; ...probe points... ;M557 P2 X200 Y165 ; ...for bed... ;M557 P3 X200 Y0 ; ...levelling ;M557 P4 X141 Y82.5 ; 5th probe point for levelling (un-comment this to get a 5th point at the centre of the bed) ; Epilogue ;*** If you are using axis compensation, put the figures in the following command ;M556 S78 X0 Y0 Z0 ; Axis compensation here T0I will check the output voltage of the PSU tonight.
I am not using ferrules on the power connectors, I just used the bare wire.
I bought it from ZYLTech about 1.5 years ago.
-
Ok, I just checked the voltage while it's printing, coming straight off the PSU, it's bouncing around between 23.9v and 24v. Is that enough to cause an issue?
I am running a print now, and will upload the results from M122 if/when it fails.
-
Checking the Vin on the Duet (from DWC), I see it dropping down to 23.6v. Is that enough to be an issue?
Thanks!
-
Ok, it just reset after about 1.5 hours of printing. Here is the output from M122:
m122 === Diagnostics === RepRapFirmware for Duet 2 WiFi/Ethernet version 3.3 (2021-06-15 21:44:54) running on Duet WiFi 1.02 or later Board ID: 08DGM-9T6BU-FG3SS-6JTD6-3S86N-KATBF Used output buffers: 3 of 24 (12 max) === RTOS === Static ram: 23876 Dynamic ram: 75000 of which 0 recycled Never used RAM 15540, free system stack 184 words Tasks: NETWORK(ready,13.4%,252) HEAT(delaying,0.0%,314) Move(notifyWait,0.1%,340) MAIN(running,86.0%,442) IDLE(ready,0.5%,29), total 100.0% Owned mutexes: WiFi(NETWORK) === Platform === Last reset 00:03:59 ago, cause: software Last software reset at 2021-06-21 22:07, reason: StuckInSpinLoop, GCodes spinning, available RAM 12412, slot 2 Software reset code 0x4083 HFSR 0x00000000 CFSR 0x00000000 ICSR 0x0041f80f BFAR 0xe000ed38 SP 0x2000232c Task MAIN Freestk 764 ok Stack: 0042ae6f 004545d8 610f0000 3f800000 4107721b 369dc3a0 3edbc06f 3331bb4c 40000000 b5ddd98d 388ab355 bb360b61 3e2aaaab 3f800000 00000000 43aa028f 4354c416 3f800000 3f800000 60000010 00000000 00000000 0042ae6f 00000001 000021e0 00000000 20000c60 Error status: 0x00 Aux0 errors 0,0,0 Step timer max interval 0 MCU temperature: min 42.5, current 42.7, max 44.5 Supply voltage: min 23.9, current 24.0, max 24.2, under voltage events: 0, over voltage events: 0, power good: yes Heap OK, handles allocated/used 0/0, heap memory allocated/used/recyclable 0/0/0, gc cycles 0 Driver 0: position 0, standstill, SG min/max not available Driver 1: position 0, standstill, SG min/max not available Driver 2: position 0, standstill, SG min/max not available Driver 3: position 0, standstill, SG min/max not available Driver 4: position 0, standstill, SG min/max not available Driver 5: position 0 Driver 6: position 0 Driver 7: position 0 Driver 8: position 0 Driver 9: position 0 Driver 10: position 0 Driver 11: position 0 Date/time: 2021-06-21 22:12:13 Cache data hit count 4294967295 Slowest loop: 149.32ms; fastest: 0.17ms I2C nak errors 0, send timeouts 0, receive timeouts 0, finishTimeouts 0, resets 0 === Storage === Free file entries: 10 SD card 0 detected, interface speed: 20.0MBytes/sec SD card longest read time 52.5ms, write time 0.0ms, max retries 2 === Move === DMs created 83, maxWait 0ms, bed compensation in use: none, comp offset 0.000 === MainDDARing === Scheduled moves 0, completed moves 0, hiccups 0, stepErrors 0, LaErrors 0, Underruns [0, 0, 0], CDDA state -1 === 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 -1 -1, chamberHeaters = -1 -1 -1 -1 Heater 1 is on, I-accum = 0.0 === GCodes === Segments left: 0 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 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 Daemon is idle in state(s) 0 Autopause is idle in state(s) 0 Code queue is empty. === Network === Slowest loop: 668.47ms; fastest: 0.00ms 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 0 WiFi firmware version 1.26 WiFi MAC address cc:50:e3:69:07:05 WiFi Vcc 3.34, reset reason Power up WiFi flash size 4194304, free heap 27064 WiFi IP address 192.168.1.231 WiFi signal strength -70dBm, mode 802.11n, reconnections 0, sleep mode modem Clock register 00002002 Socket states: 0 0 0 0 0 0 0 0Any ideas?
Thanks again for your help.
-
@mrawesome987 said in Duet 2 Wifi Random Resets:
I am not using ferrules on the power connectors, I just used the bare wire.
Might want to give those a tighten, just in case. Bare wire can loosen over time. However the M122 doesn't say that the power was lost, so that might not be it at all.
Will have to see if there is anything useful from that M122 report for DC42.
-
@phaedrux Ok, thanks for the information. I will certainly tighten the power connectors. Hopefully DC42 may have some more info on this.
Just to further reduce points of failure, I think I will get a replacement SD card. I am not using the shipped SD card, as it was so small. I believe I am running a full size SD card in the PanelDue.
What is the recommended model for a larger Micro SD? Would this work?
Thanks again!
-
Yes that would be a good SD card choice. Be sure to format it as FAT32.
-
@mrawesome987 said in Duet 2 Wifi Random Resets:
I believe I am running a full size SD card in the PanelDue.
Do you mean to say you are using an SD card in the PanelDue to print from?
-
@phaedrux said in Duet 2 Wifi Random Resets:
Do you mean to say you are using an SD card in the PanelDue to print from?
I believe that is correct. I can check when I get home tonight, but I'm fairly certain I used a 16 or 32 gb card in the PanelDue to print from, since it was on hand.
-
Can you also compare uploading a gcode file to print directly to the SD card internal to the Duet and see if it still resets?
-
@phaedrux said in Duet 2 Wifi Random Resets:
Can you also compare uploading a gcode file to print directly to the SD card internal to the Duet and see if it still resets?
I will do this tonight. I also ordered a tool for the ferrules you recommended, just for peace of mind.
-
Ok, I was wrong. I am not using an SD card in the PanelDue, I was, however, using a no name brand SD card in the Duet. I have now followed the SD card setup instructions and used a different card (although still a no name 128mb one, until my new one gets here).
I am starting the print now, and will let you know what happens.
Thanks again for your help!
-
@mrawesome987 those no name 128mb ones that probably came with a BTT are only good for one thing ... throwing in the bin.
They ALWAYS cause trouble on the LPC/STM port of RRF -
@jay_s_uk said in Duet 2 Wifi Random Resets:
@mrawesome987 those no name 128mb ones that probably came with a BTT are only good for one thing ... throwing in the bin.
They ALWAYS cause trouble on the LPC/STM port of RRFGood news! The printer completed a print last night, it was about a 5-6 hour print. This is with the no name 128mb card, but I'll swap it out for the new one when it gets here.
On the card I had in the Duet prior, I tried the same exact print (same gcode) 3 or 4 times, and it failed within 2 hours every time.
I'll continue to test and update.
-
I got the new SD card yesterday and formatted it and copied my current file structure to it. Printed a bracket for my new printer build and it worked great. It was a fairly small print, only 3-4 hours, but it printed with no issues.
I guess this is resolved, unless it magically reappears later! Thanks for the help.
-
@mrawesome987 thanks for the update. I think the firmware must have been stuck in a loop in the Atmel/Microchip SD card driver waiting for the hardware to become ready; although in theory the transfer should time out instead.
