Duet Mini 5 randomly dropping connection
-
@Dark-Monk can you try and grab and M122 output from the affected machine when its connected to your wifi network?
you can do that over usb if thats easier -
When I power up the card, I get the green light blinking steady, then flickering, then on constantly. About the same time as the green light becomes constant, a red light close by, starts flashing at a constant pace (not sure if that is normal or not).
Please refer to the LEDs with their names - else we have to guess who’s flashing:
Have you followed the WiFi troubleshooting guide?
-
I had to connect with a USB to my PC and use YAT to get an M122 command. However, once it was connected, the wifi started working again. So the below M122 is while the wifi was working.
m122
=== Diagnostics ===
RepRapFirmware for Duet 3 Mini 5+ version 3.4.6 (2023-07-21 14:09:13) running on Duet 3 Mini5plus WiFi (standalone mode)
Board ID: 22TU0-JT8LU-F65J0-409NN-1R03Z-7DKRL
Used output buffers: 1 of 40 (17 max)
=== RTOS ===
Static ram: 103712
Dynamic ram: 110568 of which 0 recycled
Never used RAM 27432, free system stack 142 words
Tasks: NETWORK(ready,13.4%,414) HEAT(notifyWait,0.0%,358) Move(notifyWait,0.0%,363) CanReceiv(notifyWait,0.0%,941) CanSender(notifyWait,0.0%,335) CanClock(delaying,0.0%,342) TMC(notifyWait,0.0%,124) MAIN(running,85.8%,406) IDLE(ready,0.0%,30) AIN(delaying,0.8%,272), total 100.0%
Owned mutexes: WiFi(NETWORK) USB(MAIN)
=== Platform ===
Last reset 00:03:15 ago, cause: power up
Last software reset at 2023-11-21 16:34, reason: User, GCodes spinning, available RAM 23832, slot 0
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 196077, completed 196077, timed out 0, errs 0
Step timer max interval 738
MCU temperature: min 32.2, current 32.2, max 33.3
Supply voltage: min 0.7, current 0.7, max 0.7, under voltage events: 0, over voltage events: 0, power good: no
Heap OK, handles allocated/used 0/0, heap memory allocated/used/recyclable 0/0/0, gc cycles 0
Events: 0 queued, 0 completed
Driver 0: ok, SG min n/a, read errors 0, write errors 0, ifcnt 0, reads 0, writes 0, timeouts 0, DMA errors 0, CC errors 0
Driver 1: ok, SG min n/a, read errors 0, write errors 0, ifcnt 0, reads 0, writes 0, timeouts 0, DMA errors 0, CC errors 0
Driver 2: ok, SG min n/a, read errors 0, write errors 0, ifcnt 0, reads 0, writes 0, timeouts 0, DMA errors 0, CC errors 0
Driver 3: ok, SG min n/a, read errors 0, write errors 0, ifcnt 0, reads 0, writes 0, timeouts 0, DMA errors 0, CC errors 0
Driver 4: ok, SG min n/a, read errors 0, write errors 0, ifcnt 0, reads 0, writes 0, timeouts 0, DMA errors 0, CC errors 0
Driver 5: ok, SG min n/a, read errors 0, write errors 0, ifcnt 0, reads 0, writes 0, timeouts 0, DMA errors 0, CC errors 0
Driver 6: ok, SG min n/a, read errors 0, write errors 0, ifcnt 0, reads 0, writes 0, timeouts 0, DMA errors 0, CC errors 0
Date/time: 1970-01-01 00:00:00
Cache data hit count 388276249
Slowest loop: 4.67ms; fastest: 0.12ms
=== Storage ===
Free file entries: 10
SD card 0 detected, interface speed: 22.5MBytes/sec
SD card longest read time 3.1ms, write time 0.0ms, max retries 0
=== Move ===
DMs created 83, segments created 0, maxWait 0ms, bed compensation in use: none, comp offset 0.000
=== MainDDARing ===
Scheduled moves 0, completed 0, hiccups 0, stepErrors 0, LaErrors 0, Underruns [0, 0, 0], CDDA state -1
=== AuxDDARing ===
Scheduled moves 0, completed 0, hiccups 0, stepErrors 0, LaErrors 0, Underruns [0, 0, 0], CDDA state -1
=== Heat ===
Bed heaters 0 -1 -1 -1, chamber heaters -1 -1 -1 -1, ordering errs 0
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 ready with "m122" 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 1021, received 0, lost 0, boc 0
Longest wait 0ms for reply type 0, peak Tx sync delay 0, free buffers 18 (min 18), ts 567/0/0
Tx timeouts 0,0,567,0,0,454 last cancelled message type 4514 dest 127
=== Network ===
Slowest loop: 100.63ms; fastest: 0.06ms
Responder states: HTTP(0) HTTP(0) HTTP(0) HTTP(0) FTP(0) Telnet(0)
HTTP sessions: 0 of 8
= WiFi =
Interface state: active
Module is connected to access point
Failed messages: pending 0, notready 0, noresp 4
WiFi firmware version 1.27
WiFi MAC address d8:bf:c0:14:e9:0a
WiFi Vcc 3.40, reset reason Power up
WiFi flash size 2097152, free heap 25792
WiFi IP address 192.168.50.175
WiFi signal strength -68dBm, mode 802.11n, reconnections 0, sleep mode modem
Clock register 00002002
Socket states: 0 0 0 0 0 0 0 0
ok -
@infiniteloop The blinking light is the LED status light. This is a Duet 3 mini 5 (not the image posted). Thank you for any help you can offer. The LED status light blinks if it is or isn't connecting to my PC.
-
All of the power LED lights, the LED V_Fused and LED_ESP light are all lit up. The LED Status light is blinking with a steady rhythm. With these lit, the wifi connection is not working. This is running on the power supply currently.
It often gets to where you can see the interface in the background, but it hasn't fully loaded. It says "transferring data from <the ip address>" in the bottom left of the browser.
So its like it does connect, but just barely and maybe the connection is really really bad. But other times it works great and is super responsive.
-
WiFi signal strength -68dBm, mode 802.11n, reconnections 0, sleep mode modem
Your signal strength isn't that great. See the list of suggested remedies here: https://docs.duet3d.com/en/User_manual/Troubleshooting/WiFi_troubleshooting
Also worth checking your SD card isn't getting full, or failing. Start by running through the checks here: https://docs.duet3d.com/en/User_manual/RepRapFirmware/SD_card#troubleshooting-sd-card-issues
Ian
Cartesian bed-slinger with Duet 3 Mini 5+ WiFi and 1LC : RRP Fisher Delta v1 with Duet 2 Maestro : TronXY X5S with Duet 3 MB6HC and Roto toolboard
-
@Dark-Monk Have you made sure the antenna is connected to the board. That little U.fl plug can wedge against the metal can of the WiFi device and feel like it is connected. Since only one is acting up , how close is it to something like a microwave or wireless phone? Mine does not like Vtech phones. I had to trade with a different brand to stop it from dropping WiFi. And you might be surprised at how the WiFi signal strength can vary even in an open room. You could download a WiFi Signal Strength Meter app and try it near the board and see how strong the signal is.
-
@droftarts - I will try moving it closer to the router, but both of my other two Duet WiFi printers are running great and I haven't seen a single problem from them. They are also seeing that same signal strength.
I reformatted the SD card as part of the trouble shooting to try to fix this problem. Did that as part of updating the firmware. It was having the same problems before and after all of that. The SD card has a ton of space on it now.
Good guesses though, thank you.
-
@KenW I can open the case and confirm, but that I am seeing a descent signal strength, kind of tells me the antenna is connected fine. I do remember it being a pain to get connected properly when I put it all together though. There isn't anything right beside the unit where it usually sits, and I have moved it around during the trouble shooting process and it is having the same problems everywhere I have put it so far. It really sucks that they are intermittent.
But currently it won't connect no matter how I power it, or where I set the card up at. I have a spare card that I am tempted to put on and see. But that's a pain but might be my only option.
-
@Dark-Monk Are your other boards Duet 2 WiFis or Duet 3 Mini 5+ WiFi?
Ian
-
@droftarts They are Duet 2 - WiFi
-
OK... might be solved / dump builder / user. I examined the antenna closely, and it might be that the case I have this is has such a thick wall, that the antenna screw in base, was just barely sticking out enough to have the antenna screw in to it. It might have been loosening up or jiggled around just a bit in the last few months and that is why it has been getting worse and worse.
I only solved this, because I was looking that the signal strength, through YAT, when it wouldn't connect. That was because of you folks pointing that out and me focusing a lot more on it. THANK YOU SO MUCH.
I'm not 100% sure this is going to fix it, but it is connecting atm and the signal strength is -64 on average. Which should work fine, but we will see.
