Duet wifi lost web connection

dc42

Does it work again if you refresh the browser page?
Next time it happens, please connect a PC running e.g. YAT or Pronterface via USB, send M122, and post the report here. Then send M552 S-1 followed by M552 S1, wait for it to connect to your WiFi network, and see whether you can connect DWC again. These will help identify whether the issue is in the WiFi module or the main firmware.

avaradus

After refresh browser page nothing changed and still not work.

I think wifi module works, and problem in main firmware.
After reset printer with command M999 start works normal.

I'm connect via USB and that result
0_1555732305691_rs.txt

avaradus

@dc42 See the video https://youtu.be/psSlSt5nMyk
I'm trying send command M122 but result is truncated and not full =(

whosrdaddy

@avaradus use YAT instead of Pronterface (and don't forget to set the line ending to <LF> in YAT)

avaradus

@whosrdaddy Trying YAT and nothing changes. IMHO problem in firmware, does not send complete data.

Adrian52

I have a similar sounding problem, using a 1.01 duet wifi and most recent rc firmware, dwc2. When connection is lost, even rebooting the host PC and restarting browser (firefox) doesn't help. The print continues to finish perfectly. With YAT, M122 gives no response (on earlier occasions I have had a truncated response). M552 S-1 switches off the wifi, and M552 S1 switches it on, but still no connection. Board responds to M999 with reset, but M122 then gives a partial response and halts YAT with the error message 'an unhandled asynchronous non synchronised exception occurred while running YAT' the detailed info 0_1556045927327_20190423_yat_exception.txt
On restarting YAT, M122 then works fine.

dc42

YAT can be a bit funny when the USB COM port disappears and the reappears, as it does when you reboot the Duet.

My guess is that the Duet is running out of buffer RAM, but I don't know why.

@Adrian52 , which versions of firmware (main and WiFi) exactly are you running? How many PC/tablets/smartphones are or have accessed the Duet since it was originally powered on or reset?

Adrian52

@dc42 I am on main 2.03beta3(2019-03-25b6), WiFi 1.23, dwc 2.0.0rc6. I am only connecting via win10 pc/Firefox - deleted the duet app from phone and tablet at the moment, to eliminate concurrent connections.
Have the impression that this is a progressive thing - I initially get no response to M122, then M122 triggers a disconnect /reconnect, then connection is lost with multiple retrys from dwc.

dc42

It's possibly a progressive loss of message buffers, which prevents both a full status response to DWC and a full M122 report.

Is it any different if you use DWC 1.22.6 instead of DWC2? You can revert to DWC 1.22.x just by putting "/reprap.htm" after the Duet IP address in your browser address bar.

Adrian52

@dc42 same behaviour when using dwc 1.22 with the ip/reprap.htm method

dc42

I guess I'll have to start leaving my printers on overnight to see if I can reproduce this. Does the problem occur if you leave the printer idle for 2-3 days, or only if it is printing?

Adrian52

@dc42 away for the weekend - will check next week

Adrian52

@adrian52 I think I may have found the answer for my issue - this comment on a thread yesterday rang a bell:

gnydick 1 May 2019, 07:33

One possibility. I found I have a DC power brick plugged into the same circuit that is SQUEEEEELING, I think a cap is ready to blow. That could be interfering.

I had a noisy DC brick supplying a desk lamp next to the duet. Since I unplugged it, I have had the printer on all day with no lost connection or failed M122

Phaedrux

@adrian52 said in Duet wifi lost web connection:

I had a noisy DC brick supplying a desk lamp next to the duet. Since I unplugged it, I have had the printer on all day with no lost connection or failed M122

That's interesting. Why would that be?

avaradus

@dc42 In my case, this happens when it is printing

dc42

@avaradus said in Duet wifi lost web connection:

@dc42 See the video https://youtu.be/psSlSt5nMyk
I'm trying send command M122 but result is truncated and not full =(

Does it get as far as displaying the "Used output buffers" bit? That's the 4th line down from the top.

avaradus

@dc42 Yes, that is right 20 of 20 max. How can i increase the number of buffers?

dc42

I will increase the number of buffers in the 2.03 release, however I am not sure that increasing the number of buffers is the solution. The question is, why are all the buffers allocated and not getting released?

Do you access the Duet via the web interface from a single device (PC/tablet/smartphone), or from multiple devices? Many firmware versions ago there was a problem with buffer management if you turned a device off without disconnecting it from the Duet in DWC first; but that was fixed (it now times out and releases the buffers for that client after 10 seconds of inactivity form the client).

You can monitor the number of buffers when the machine is idle. When I run M122 from DWC with just a single web client and an attached PanelDue, it reports either 1 or 3 buffers allocated.

avaradus

@dc42 I have only one computer and one connection to the web interface.
DWC too often sends requests. When many requests fail, repetitions are performed without a timer delay. IMHO at this moment buffers overflow.

dc42

@avaradus, I'll ask chrishamm how long DWC waits for a response before timing out and sending another request.

Next time this happens, please try closing the browser tab that DWC is open in. Then wait more than 10 seconds, and after that either use YAT to send M122 and check whether the buffers have been released, or try reloading DWC. What should happen is that if DWC doesn't receive any traffic from an IP address in 10 seconds, it should time out that client and release any associated buffers.