Duet wifi file upload browser dependent

old-relic

My Duet wifi controller will not upload g-code files when the browser used is either Chrome or Firefox.
The error reported is "network error"
If I use Microsoft Edge, files upload reliably every time without error.
I can also FTP files to the duet.
Any help will be much appreciated as Edge is not my favorite browser.

Veti

are you on the latest firmware and dwc?

old-relic

Firmware Version:
2.03 (2019-06-13b2)

Web Interface Version:
1.22.6

T3P3Tony

that is strange and chrome and firefox are the most common browsers used here and they ar eboth known to work (safari not so much, at least in old releases)

old-relic

@t3p3tony Hi,
well, (sadly) they don't work where I live.

T3P3Tony

how are you connecting to the duet (IP address or machinename.local?) are those browsers setup to use a proxy server or something like that? network error is weird if you can connect to it from edge

old-relic

@t3p3tony
I was using the ipaddress to access the DWC. My machine name was a bit unwieldly and might have had illegal characters in it so I have never tried accessing the DWC that way. I will change the machine name in config.g and try machinename.local.

Also, no proxy servers are involved.

T3P3Tony

@old-relic the IP should work in any browser it was the .local method I thought could be causing issues.

Wonder if it's some chrome restriction because it's not an HTTPS site..

old-relic

@t3p3tony
The problem seems to be with Firefox too.
I tried removing Chrome from my PC with Revo Uninstaller which does a thorough job of cleaning up any leftovers the normal uninstall leaves behind.
Then I did a fresh install of Chrome but the problem remains.
I guess it has to be some weirdness about my system if others aren't having the problem.

Veti

do you have access to a different pc. like a laptop from a friend.
this way you can check if it your pc that is causing the problem

chas2706

Hi
I have a slightly different issue. If I use chrome I often get this kind of response:

09:05:53: Connection established!
09:05:25: Disconnected.
09:05:11: Connection established!
09:04:13: Disconnected.
09:04:00: Connection established!
09:03:31: Disconnected.
09:03:20: Connection established!
09:03:02: Disconnected.
09:02:49: Connection established!
09:02:27: Disconnected.
09:02:08: Connection established!
09:01:50: Disconnected.
09:01:16: Connection established!
09:01:09: Disconnected.
09:00:45: Connection established!
09:00:27: Disconnected.
08:59:53: Connection established!
08:59:26: Disconnected.
08:59:15: Connection established!
08:59:15: Page Load complete!

But if I use Microsoft Edge I never experience disconnection problems.
My board is Duet 2 Ethernet.

Veti

@chas2706
have you checked that you did not use an ip that is already in use?

chas2706

@Veti

Yes I have given it a static ip that is not in use by anything else. I get the same connection problems if I use Firefox too and file uploads in both Firefox and Chrome are amazingly slow.
Again using Microsoft Edge I don't get these problems. No disconnections and fast file uploads.

dc42

A Wireshark trace might help diagnose the reason.

chas2706

TBH the positives of the duet board in my opinion and in descending order are:

Accessability via the web
The ability to change settings on the fly
Super quiet stepper motors
Monitor printing via webcam

And the negatives are:

Web accesability can be problematic
File upload speed can be problematic
Connection can vary dependant on browser in use
Duet is not capable of direct web cam connection
Webcam connection can often fail to connect in duet browser even though it can be accessed in a new window via it's ip address

My Duet Ethernet was purchased from Duet 3D. Previously I had a duet wifi (cloned from china). The Duet wifi was complete rubbish regarding internet connection so I thought surely I can't go wrong if I purchase a genuine Duet Ethernet from Duet 3D.

My issue is that I have many internet connected devices of which never loose connection (unless the server goes down), so what is so special or so wrong with the Duet board?
Just search "Duet connection problems" on the forum to see how big this issue is.

In contrast, last month I spent £220 on a Creality Ender 3 Pro and without any mods whatsoever I can not fault this printer despite there being no direct internet access etc.
I guess in comparison the control board costs about £40.

mwolter

Looks to me that you could have an intermittent network issue with your computer and possibly the Duet. The webcam network traffic bypasses the Duet completely so if your browser can't open the webcam there is an issue between your PC and the webcam. I'd start by taking a closer look at your network. Also, might try replacing the SD card with a well known brand. I've had similar file upload speed issues and also issues where larger files would not upload reliably until the SD card was replaced.

old-relic

@veti Hi, it looks like the my topic is getting slightly hijacked. But yes, I have a laptop I can use and I will try that.

old-relic

@t3p3tony
Hi
I copied my set of g-code files over to a Thinkpad.
There were a set of 20 g-code files of various sizes from a few KB to 33 MB
I had ONE failure , the same one I have been seeing on my workstation PC (Dell T7500). It happened at my first attempt to upload to the Duet from the ThinkPad.

After that, I had 19 successful uploads

So then I went back to the workstation and decided to copy the g-code file set from Hard Drive F onto Drive C, a solid state drive.

Using a Chrome browser, I was now able to upload the file set with no more errors, they were gone.

I then used Firefox which also had previously failed and again the files uploaded with no problem.

Finally, I went back to loading from Drive F and using both Chrome and Firefox I was successful in loading all the files without error.

The problem seems to have sorted itself out overnight. I did nothing to solve the problem other than what I have outlined above.

Magically, I can now use Chrome or Firefox to upload to the Duet, go figure. I hope it stays fixed.

FM as they used to say in Customer Support

T3P3Tony

@old-relic thanks for the update, I see what would cause the behaviour you observed. Hopefully it stays fixed!