Duet 2 Wifi rebooting/crashing during print

dc42

@bwnance, your M122 software reset data doesn't make any sense, so I think it must have been caused by a transient or possible power brownout. Can you run a few more prints to see if any future crashes are similar? You can do air prints to avoid wasting filament.

The assertion failure you had with 3.2beta4 is different, that's a known bug that was fixed in 3.2beta4.1.

bwnance

@dc42 Will do dry-runs throughout today. It's weird, sometimes it completes a print just fine, sometimes it fails -- but all with the same file.

@Veti

hackinistrator

motors very close to the board .
maybe try to add some shielding , or relocate the board just for a test .

bwnance

@dc42 crash on a no-filament run:

m122
=== Diagnostics ===
RepRapFirmware for Duet 2 WiFi/Ethernet version 3.2 running on Duet WiFi 1.02 or later
Board ID: 08DJM-9178L-L2MSD-6J1FA-3S46N-KSFYP
Used output buffers: 3 of 24 (11 max)
=== RTOS ===
Static ram: 23460
Dynamic ram: 72744 of which 24 recycled
Never used RAM 15852, free system stack 191 words
Tasks: NETWORK(ready,182) HEAT(blocked,309) MAIN(running,452) IDLE(ready,19)
Owned mutexes: WiFi(NETWORK)
=== Platform ===
Last reset 00:01:26 ago, cause: software
Last software reset at 2021-01-08 15:42, reason: HardFault imprec, GCodes spinning, available RAM 15608, slot 0
Software reset code 0x4063 HFSR 0x40000000 CFSR 0x00000400 ICSR 0x00400003 BFAR 0xe000ed38 SP 0x2001ffa8 Task MAIN Freestk 29378 ok
Stack: 20008e54 20008e50 1cc5b538 00000004 0000000a ffffffed 0040f1f8 010f001f 20008e54 20003440 20008110 20004494 a5a5a5a5 ffffffed 00000000 00f00000 e000ef34 c0000000 20004690 004548f5 0045465c 61000000 ffffffff ffffffff ffffffff ffffffff ffffffff
Error status: 0x00
Aux0 errors 0,0,0
MCU temperature: min 24.0, current 24.4, max 25.2
Supply voltage: min 23.9, current 24.1, max 24.3, under voltage events: 0, over voltage events: 0, power good: yes
Driver 0: position 62528, standstill, SG min/max not available
Driver 1: position 62528, standstill, SG min/max not available
Driver 2: position 62528, 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-01-08 15:43:37
Cache data hit count 105466486
Slowest loop: 4.99ms; fastest: 0.20ms
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 1.1ms, write time 0.0ms, max retries 0
=== 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
=== 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: 16.01ms; 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.25
WiFi MAC address dc:4f:22:6e:6c:ca
WiFi Vcc 3.43, reset reason Turned on by main processor
WiFi flash size 4194304, free heap 22320
WiFi IP address 192.168.86.34
WiFi signal strength -55dBm, mode 802.11n, reconnections 0, sleep mode modem
Clock register 00002002
Socket states: 0 0 0 0 0 0 0 0

bwnance

Anotha one.

M122
=== Diagnostics ===
RepRapFirmware for Duet 2 WiFi/Ethernet version 3.2 running on Duet WiFi 1.02 or later
Board ID: 08DJM-9178L-L2MSD-6J1FA-3S46N-KSFYP
Used output buffers: 3 of 24 (11 max)
=== RTOS ===
Static ram: 23460
Dynamic ram: 72744 of which 24 recycled
Never used RAM 15852, free system stack 193 words
Tasks: NETWORK(ready,194) HEAT(blocked,307) MAIN(running,456) IDLE(ready,19)
Owned mutexes:
=== Platform ===
Last reset 00:00:21 ago, cause: software
Last software reset at 2021-01-08 16:41, reason: HardFault invState, GCodes spinning, available RAM 15608, slot 1
Software reset code 0x4063 HFSR 0x40000000 CFSR 0x00020000 ICSR 0x0041f803 BFAR 0xe000ed38 SP 0x200043e0 Task MAIN Freestk 976 ok
Stack: 00000002 200099c0 00000100 00000000 200178b8 0042d68f 00000000 600f0000 0042d75a 610f0000 ffffffff 0000000a 010095c8 20008e54 00000000 00000000 00000000 00454a15 20008e54 00000000 20008e54 00454daf 200099c4 00454f3b 00000000 ffffffff 200099c0
Error status: 0x00
Aux0 errors 0,0,0
MCU temperature: min 24.0, current 24.6, max 25.0
Supply voltage: min 24.0, current 24.0, max 24.2, under voltage events: 0, over voltage events: 0, power good: yes
Driver 0: position 62528, standstill, SG min/max not available
Driver 1: position 62528, standstill, SG min/max not available
Driver 2: position 62528, 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-01-08 16:42:20
Cache data hit count 25138224
Slowest loop: 4.94ms; fastest: 0.20ms
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 1.1ms, write time 0.0ms, max retries 0
=== 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
=== 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: 15.68ms; 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.25
WiFi MAC address dc:4f:22:6e:6c:ca
WiFi Vcc 3.43, reset reason Turned on by main processor
WiFi flash size 4194304, free heap 22400
WiFi IP address 192.168.86.34
WiFi signal strength -57dBm, mode 802.11n, reconnections 0, sleep mode modem
Clock register 00002002
Socket states: 0 0 0 0 0 0 0 0

bwnance

@hackinistrator Moved the board over and repositioned the berdair to be nowhere near the board... we shall see.

hackinistrator

@bwnance
so?

bwnance

@hackinistrator haven't had a bunch of time, but i've run 3 dry runs so far with no issue - a pretty good sign.

dc42

Is the Berdair driven directly from a Duet heater output? If so then I suggest twisted pair wires between the two. Hand twisted will do.

Have you connected a fast recovery flyback diode in parallel with the Berdair? The best place for it is on the motor terminals. Make sure you connect it the right way round!

bwnance

@dc42 the Berdair is connected directly to FAN0 -- i was under the impression that a flyback diode had been included on all the fan headers in recent board revisions - i might have misunderstood?

bwnance

@dc42 just got another crash -- should i have the berdair wired differently than i do now?

m122
=== Diagnostics ===
RepRapFirmware for Duet 2 WiFi/Ethernet version 3.2 running on Duet WiFi 1.02 or later
Board ID: 08DJM-9178L-L2MSD-6J1FA-3S46N-KSFYP
Used output buffers: 3 of 24 (11 max)
=== RTOS ===
Static ram: 23460
Dynamic ram: 72744 of which 24 recycled
Never used RAM 15852, free system stack 191 words
Tasks: NETWORK(ready,188) HEAT(blocked,307) MAIN(running,452) IDLE(ready,19)
Owned mutexes: WiFi(NETWORK)
=== Platform ===
Last reset 00:01:26 ago, cause: software
Last software reset at 2021-01-26 23:27, reason: HardFault invState, GCodes spinning, available RAM 15608, slot 1
Software reset code 0x4063 HFSR 0x40000000 CFSR 0x00020000 ICSR 0x0041f003 BFAR 0xe000ed38 SP 0x2001ffc0 Task NETW Freestk 31192 ok
Stack: 400a4000 2000222c 00000003 00000001 200000ac ffffffed 00000000 200f000e 00000000 00f00000 e000ef34 c0000000 20004690 004548f5 0045465c 61000000 ffffffff ffffffff ffffffff ffffffff ffffffff ffffffff ffffffff ffffffff ffffffff ffffffff ffffffff
Error status: 0x00
Aux0 errors 0,0,0
MCU temperature: min 25.0, current 25.3, max 26.1
Supply voltage: min 24.0, current 24.1, max 24.2, under voltage events: 0, over voltage events: 0, power good: yes
Driver 0: position 62532, standstill, SG min/max not available
Driver 1: position 62532, standstill, SG min/max not available
Driver 2: position 62532, 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-01-26 23:28:54
Cache data hit count 106076577
Slowest loop: 6.33ms; fastest: 0.20ms
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 1.0ms, write time 0.0ms, max retries 0
=== 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
=== 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: 15.65ms; 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.25
WiFi MAC address dc:4f:22:6e:6c:ca
WiFi Vcc 3.43, reset reason Turned on by main processor
WiFi flash size 4194304, free heap 19328
WiFi IP address 192.168.86.20
WiFi signal strength -36dBm, mode 802.11n, reconnections 0, sleep mode modem
Clock register 00002002
Socket states: 0 0 0 0 0 0 0 0

dc42

@bwnance said in Duet 2 Wifi rebooting/crashing during print:

@dc42 the Berdair is connected directly to FAN0 -- i was under the impression that a flyback diode had been included on all the fan headers in recent board revisions - i might have misunderstood?

We don't advise connecting a Berdair directly to a fan port. The starting current of the motor will exceed the peak rated current of the fan mosfet, causing it to fail after a while.

bwnance

@dc42 I connected the EZ-Switch that the berdair comes with to an unused heater block + a fan header -- This appears to have solved the crashing issues.

Using any high PWM frequency after this ended up resulting in "all or nothing" fan control -- i dropped the frequency down to 20hz and that seems to have solved the issue, though.

dc42

Thanks for the update! I'm glad the problem is solved. I'll mark this as solved, but feel free to un-mark it if the problem recurs.

bwnance

@dc42 thank you so much for the support! I really appreciate it

Robthide37

@dc42 and @Phaedrux and @bwnance please correct me if i am wrong i am going to be adding my ez out switch now to as i was under the impression the 1 amp plus 50 percent for start was still ok for the mosfet on fan0 but anyway i plan on swithing to a brushless pump anyway as i found a kvp8 pump that flows a large amount and can run series or parallel.
I run berd air as well and two things the pump is very noisy it actually can make my camera get artifacts from the emi. Also if you remove the flux ring you will increase rpm as we are not running a high pressure system. Last why are you using a heater block oyu should be connecting 24v constant to the ez pwm board then use the fan output. The only time you would do what you listed would maybe be with a brushless motor that has built in controller and you wanted to run 3wire or try and run a 4 wire with tach but in that situation i would think you would use and endstop output to pwm control the brushless pump so that it only gets 5v unless you want to run all fans at 5v. I say that cause most things do not like the 24v pwm control signal.

dc42

Brushed DC motors usually take much more than 50% extra current when starting. More like 500%. Brushless motor have much lower starting currents.

Robthide37

@dc42 Ohhh thankyou i did not know that i was just using the info from my generator and my well pump starting load vs running load lol

Solved Duet 2 Wifi rebooting/crashing during print