Random disconnects DuetWifi 3.01 RC12
-
I just updated to RC12 as well as updating to DuetWifiServer1.23 and DuetWebControl2.1.7 and am still having the same problem.
So far I haven't been able to start a print yet but for instance while homing when it disconnects the printer stops and sometimes I get a message saying "Connection lost attempting to reconnect" other times there's no message and the homing button on web control just shows a spinning circle on it. Occasionally it will reconnect and continue but most of the time the web control page just goes back to as if I just connected to the printer.
The disconnects aren't consistent either sometimes it happens while the printer is moving and sometimes while the printer is idle.
-
Alright. I've moved this to the beta firmware forum.
If you go back to 2.05.1 do the disconnects stop?
-
Hello.
I have the same issue since I upgrade to 2.05.1.
I run before 2.04 betaWhen I switch to another tab of my browser and then go back few second later to the Duet one, the UI is disconnected, and then connected back automatically
Connection interrupted, attempting to reconnect... HTTP request timed out -
@Viald said in Random disconnects DuetWifi 3.01 RC12:
When I switch to another tab of my browser and then go back few second later to the Duet one, the UI is disconnected, and then connected back automatically
This has more to do with browser tab behaviour than the duet. Most browsers now days will put unfocused tabs to sleep to save power. This behaviour can be sometimes configured in the browser. There's not much the DWC can do about it when it's the browser than has severed the connection.
-
After installing 2.05.1 the disconnects actually seem to have gotten more frequent. I now can't even home a single axis without the disconnect happening. Any time I click a home button I get a spinning circle over the home button then a message saying "connection lost, attempting to reconnect". After about 10 seconds the blue led on the wifi chip will then flash twice then stay lit. Then the printer will say "connection established" but never finish the homing cycle and goes back to as if I just turned the printer on.
-
So not related to RC12 at all then.
Please try reflashing the 1.23 wifi server firmware. You can just upload it via DWC when connected.
It may be a failing wifi module.
-
I tried reflashing the 1.23 wifi server firmware and I am still having the same problem.
Is there any way to fix or replace the wifi module if it is failing?
-
@Phaedrux Thank you. Perhaps it's due to the browser but It doesn't happen before the upgrade with the same browser.
I will check with another browser and let you know. -
Tested with Chrome, no disconnection at all
-
@mike5490 said in Random disconnects DuetWifi 3.01 RC12:
Is there any way to fix or replace the wifi module if it is failing?
Yes it can be replaced if you're handy with soldering. I believe a hot air rework station is recommended.
Check this thread out. He was able to remove it with just a soldering iron.
https://forum.duet3d.com/topic/15033/12v-on-the-5v-rail/46?_=1589482012979
-
Okay, thank you.
Is there anything else that could potentially be the problem, as I'd only like to start desoldering parts from the board as a last option or is the wifi chip the most likely cause?
-
Well we've ruled out the firmware, and your signal strength is good, you've tried another router.
Unless there is some other source of interference in the area you can identify and eliminate.
You could try switching to another wifi channel.
You can try and provide an M122 from when it's disconnected.
-
Trying multiple different wifi channels didn't seem to have any effect on it.
This is my results from M122 after it disconnects
M122
=== Diagnostics ===
RepRapFirmware for Duet 2 WiFi/Ethernet version 3.01-RC12 running on Duet WiFi 1.02 or later + DueX5
Board ID: 08DGM-956GU-DJMSN-6J1DL-3SN6M-TTNRF
Used output buffers: 3 of 24 (8 max)
=== RTOS ===
Static ram: 28084
Dynamic ram: 94064 of which 20 recycled
Exception stack ram used: 600
Never used ram: 8304
Tasks: NETWORK(ready,804) HEAT(blocked,1228) DUEX(blocked,160) MAIN(running,1820) IDLE(ready,76)
Owned mutexes: I2C(DUEX)
=== Platform ===
Last reset 00:02:19 ago, cause: power up
Last software reset at 2020-05-13 22:26, reason: Stuck in spin loop, spinning module Move, available RAM 8240 bytes (slot 2)
Software reset code 0x4084 HFSR 0x00000000 CFSR 0x00000000 ICSR 0x0041f80f BFAR 0xe000ed38 SP 0x20004344 Task IDLE
Stack: 004549dd 00455412 61000000 a5a5a5a5 004549dd a5a5a5a5 a5a5a5a5 2000436c 2000425c 00000002 20005194
Error status: 0
MCU temperature: min 24.1, current 31.2, max 31.5
Supply voltage: min 24.3, current 24.5, max 24.7, under voltage events: 0, over voltage events: 0, power good: yes
Driver 0: standstill, SG min/max not available
Driver 1: standstill, SG min/max not available
Driver 2: standstill, SG min/max not available
Driver 3: standstill, SG min/max not available
Driver 4: standstill, SG min/max not available
Driver 5: standstill, SG min/max not available
Driver 6: standstill, SG min/max not available
Driver 7: standstill, SG min/max not available
Driver 8: standstill, SG min/max not available
Driver 9: standstill, SG min/max 0/0
Date/time: 2020-05-14 15:23:48
Cache data hit count 241975993
Slowest loop: 25.44ms; fastest: 0.12ms
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 4.9ms, write time 0.0ms, max retries 0
=== Move ===
Hiccups: 0(0), FreeDm: 169, MinFreeDm: 167, MaxWait: 17823ms
Bed compensation in use: none, comp offset 0.000
=== MainDDARing ===
Scheduled moves: 16, completed moves: 16, StepErrors: 0, LaErrors: 0, Underruns: 0, 0 CDDA state: -1
=== AuxDDARing ===
Scheduled moves: 0, completed moves: 0, StepErrors: 0, LaErrors: 0, Underruns: 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
Daemon is idle in state(s) 0
Autopause is idle in state(s) 0
Code queue is empty.
=== Network ===
Slowest loop: 31624.06ms; fastest: 0.00ms
Responder states: HTTP(2) HTTP(0) HTTP(0) HTTP(0) FTP(0) Telnet(0)
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.23
WiFi MAC address 5c:cf:7f:76:68:e0
WiFi Vcc 3.42, reset reason Unknown
WiFi flash size 4194304, free heap 24696
WiFi IP address 192.168.1.101
WiFi signal strength -34dBm, reconnections 0, sleep mode modem
Socket states: 4 0 0 0 0 0 0 0
=== DueX ===
Read count 19153, 8254.12 reads/min
- WiFi -
-
Was that while disconnected or after reconnection?
-
That was after it had reconnected. Is it possible to get a readout while it’s disconnected?
-
@mike5490 said in Random disconnects DuetWifi 3.01 RC12:
That was after it had reconnected. Is it possible to get a readout while it’s disconnected?
Yes, via USB.
-
I tried to get a M122 while it's disconnected but have been unable to
Every time it disconnects the USB connection to my computer also disconnects, similar to as if I was unplugging the USB cable
-
After a bit more troubleshooting I've determined that the printer behaves as if I sent a M999 command but it occurs at random times
-
@mike5490 said in Random disconnects DuetWifi 3.01 RC12:
Every time it disconnects the USB connection to my computer also disconnects
this always happen when the board is reset.
@mike5490 said in Random disconnects DuetWifi 3.01 RC12:
I've determined that the printer behaves as if I sent a M999
running
M122first thing after connecting to the board again would be helpful. is there anything that could short against the reset pins or trigger the reset switch on the board? pictures andM122might provide some insight. -
The results from M122 immediately after it reconnects are provided above in a previous post. There's nothing that could be pressing against the reset button.
This is how the board is currently wired
