Slow Upload, high Pending?
-
I've got 6 different routers lying around together with 4 different types of interchangeable antenna-types. Tried to get a line of sight connection of about 20 meters through 2 window-glasses / 1 glass + 1 transporter-metal-wall. The results are not to fine - to be diplomatic.
5 meters behind some obstacles + wrong antenna-type and wrong height-level can already become quite problematic.
In my case the router's a meter away on the opposite site of the printer's antenna (behind printer) and 40cm above. In my case the connection theoretically shouldn't be a problem.
Just reassembled it and about to print. i'll have a look for chrome's devtools. The long time for upload's bearable, but it would be nice to have it sorted out for everybody.
-
I believe the Duet Wifi is limited to Wireless G 2.4Ghz networks. So you may have luck by forcing control over at least one router dedicated to the wireless connection to the Duet.
-
Just had a go to get another result additional to the already seen one above. Seems the micro-sd delivered with the duet is the limiting factor.
SD card 0 detected, interface speed: 20.0MBytes/sec
SD card longest block write time: 392.1ms, max retries 0=== Network ===
Slowest loop: 393.80ms; fastest: 0.01ms
WiFi signal strength -48dBm, reconnections 0, sleep mode modem -
@kolja Do you have another card to test?
-
I just tested a microSD card from microcenter, still very slow. I'm not sure what's going on here, but it's weird. Different router is my next step.
-
OK So I've just done some testing with using another router and different configurations.
I can't get rid of the original router, but I can connect up the second router as a repeater. I can connect the Duetwifi to the repeater network, and connect my laptop to the repeater network, and uploads work FAST (up to 600 KiB/s!!)(but something about comcast business class blocks DNS queries from repeaters so I don't get internet).
I can connect my laptop up to the comcast router, and keep the duetwifion the repeater network, but it seems that doing that brings the upload speed back down. There is some interaction from uploading through the comcast router.
-
Looking @ your M122-results further up, your max network-loops are just a minimum longer than your max write time for the uSD-card. Sounds to me as if the card's write-time would be the main-limiting factor.
As for my system, it's purely the uSD-card delivered with the duet. your 112ms max block write are a ferrari compared to my max 400ms i've had so far.
For negotiating the network-transfer without to much hassles i'd resort to (ignoring much more time-consuming methods):
- M122 SD max write and Network max loop
- perhaps Chrome Devtools (Ctrl + Shift + I) - network tab
Generally i'd try to avoid all unnecessary network-problems by taking the router and the printer alone without any other obstacles. If they run together properly, you can investigate to more complicated steps. If not - righdo - than at least you've got less complexity at hand.
-
Gents, just for the statistics: Max block time uSD
Card delivered with Duet3D
- 360-400ms
SanDisk uSD Ultra SDHC I 8GB
- formatted 4K (Win 7): 800ms!
- formatted 32K (SD-Formatter) : 7.9ms, 8.6 ms
I'd say, big thank you to @Phaedrux for pointing out https://www.sdcard.org/downloads/formatter_4/
-
@kolja You might even be able to get windows to use 64k clusters.
-
Would have had the possibility to format with 64K in Win7, but wanted to give the formatter a try. Results are at least amazing. Factor 100!
-
using the SD formatter on its own didn't work for me. I think my issue is a network issue because of my comcast router. My network tests were done with 64k block size so that could be helping, but I'm certain it's not the only thing at play here.
-
@rentablesocks There's definitely two possible bottlenecks. The write speed of the network interface and the write speed of the SD card.
-
@phaedrux Right, but even with the SD card formatted properly, using one network vs the other still reduces the speed to sub 50KiB/s so I think that's the primary cause.
-
@rentablesocks right. Your bottleneck is your network.
