Duet Wifi upload speed became very slow



  • I haven't been using my 3D printer for a few months. Before that I was getting pretty descent upload speed (>300kb/s).
    However when I start my Kossel again without any changes, the upload speed becomes significantly slower to about 30-50kb/s
    I tried the usual suspects, tried 2 freshly formated sd cards with 64kb cluster size and even bought a new one for testing but doesn't help.
    Clear the config file except enabling wifi, did a factor reset on my router, re-flash all firmwares (tried 2.02beta1 and 2.01) and move my duet board around but still no improvement.
    Here is my M122 and hope someone can help me spot where the problem is. Thanks

    RepRapFirmware for Duet 2 WiFi/Ethernet version 2.02beta1(RTOS) running on Duet WiFi 1.0 or 1.01
    Board ID: 08DAM-999TL-MQ4S8-6J1FJ-3SD6R-1Q8BZ
    Used output buffers: 5 of 20 (11 max)
    === RTOS ===
    Static ram: 28476
    Dynamic ram: 98332 of which 0 recycled
    Exception stack ram used: 276
    Never used ram: 3988
    Tasks: NETWORK(ready,328) HEAT(blocked,1192) MAIN(running,3548)
    Owned mutexes: WiFi(NETWORK)
    === Platform ===
    Last reset 00:05:31 ago, cause: power up
    Last software reset at 2018-08-28 18:17, reason: User, spinning module GCodes, available RAM 5968 bytes (slot 2)
    Software reset code 0x0003 HFSR 0x00000000 CFSR 0x00000000 ICSR 0x0041f000 BFAR 0xe000ed38 SP 0xffffffff Task 0x4e49414d
    Error status: 0
    Free file entries: 10
    SD card 0 detected, interface speed: 20.0MBytes/sec
    SD card longest block write time: 10.9ms, max retries 0
    MCU temperature: min 35.9, current 42.2, max 42.4
    Supply voltage: min 24.1, current 24.2, max 24.5, under voltage events: 0, over voltage events: 0
    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
    Date/time: 2018-08-31 16:42:23
    Slowest loop: 12.27ms; fastest: 0.07ms
    === Move ===
    Hiccups: 0, StepErrors: 0, LaErrors: 0, FreeDm: 240, MinFreeDm: 240, MaxWait: 0ms, Underruns: 0, 0
    Scheduled moves: 0, completed moves: 0
    Bed compensation in use: none
    Bed probe heights: 0.000 0.000 0.000 0.000 0.000
    === Heat ===
    Bed heaters = 0 -1 -1 -1, chamberHeaters = -1 -1
    Heater 1 is on, I-accum = 0.0
    === GCodes ===
    Segments left: 0
    Stack records: 2 allocated, 0 in use
    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
    serial is idle in state(s) 0
    aux is idle in state(s) 0
    daemon is idle in state(s) 0
    queue is idle in state(s) 0
    autopause is idle in state(s) 0
    Code queue is empty.
    === Network ===
    Slowest loop: 54.05ms; fastest: 0.01ms
    Responder states: HTTP(0) HTTP(0) HTTP(0) HTTP(0) FTP(0) Telnet(0) Telnet(0)
    HTTP sessions: 1 of 8
    - WiFi -
    Network state is running
    WiFi module is connected to access point
    Failed messages: pending 0, notready 0, noresp 0
    WiFi firmware version 1.21
    WiFi MAC address 60:01:94:08:62:be
    WiFi Vcc 3.35, reset reason Turned on by main processor
    WiFi flash size 4194304, free heap 14488
    WiFi IP address 192.168.1.170
    WiFi signal strength -45dBm, reconnections 0, sleep mode modem
    Socket states: 0 0 0 0 0 0 0 0
    === Expansion ===
    

    edit: a bit more information, the printer still prints fine with good quality. I did thought it was a browser issue since when it first uploads it would show something like 28MB/s and with a small file it would show it's 100% done but actually it's uploading very slow in the background and takes a long time to finish. So I tried different browsers but the results are the same.


  • administrators

    Even 300kb/sec is slower than it should be. Your WiFi signal strength look good (-45dBm). Your slowest loop time (54.05ms) is poor and that's likely related to the problem. We need to know why it is so high. The longest SD card block write time is only 10.9ms, so it looks like it's not just SD card writes that are slowing it down.

    One possible cause is having debug enabled, so please check that it is disabled. Send M111 without parameters to check.

    If you watch the upload progress indicator, does it show a steady but slow upload, or do you get bursts of progress with pauses between them?

    What make and speed class of SD card did you try?



  • I don't actually remember what the original upload speed was, probably higher than that.
    My M111 returns this

    Debugging enabled for modules:
    Debugging disabled for modules: Platform(0) Network(1) Webserver(2) GCodes(3) Move(4) Heat(5) DDA(6) Roland(7) Scanner(8) PrintMonitor(9) Storage(10) PortControl(11) DuetExpansion(12) FilamentSensors(13) WiFi(14) none(15)
    

    and here are my cards
    0_1535711675686_IMG_2054 (已編輯).JPG

    The upload progress bar jumps a bit as it starts since it always shows an upload speed >10MB/s at first, then it seems to stops there. once it catches up with the actually upload progress it would be a steady slow upload.



  • @jackal Try Sandisk Extreme if you can lay your hands on one. It might not be your problem but I've found the "Extreme" to be noticeably faster than the "Ultra" for uploading gcode files. I get a tad over 1Mb/sec but that's over wired gigabit lan, not wifi.



  • @deckingman The current upload speed is way too slow for me to consider that option. I may try flashing an older firmware to my router and see if that helps.

    @dc42 do you have any advice on what else I can try?



  • Not sure if it's related, but I started having a lot of "ERROR"s during uploads (and even when it works, it will be very slow) after upgrading from 1.21 to 2.02beta. It will eventually work if I repeat the upload.


  • administrators

    @token47 said in Duet Wifi upload speed became very slow:

    Not sure if it's related, but I started having a lot of "ERROR"s during uploads (and even when it works, it will be very slow) after upgrading from 1.21 to 2.02beta. It will eventually work if I repeat the upload.

    That's interesting. Did you upgrade DuetWiFiServer at the same time, or were you already using version 1.21? Does M122 still report a good signal strength?



  • @dc42 said in Duet Wifi upload speed became very slow:

    @token47 said in Duet Wifi upload speed became very slow:

    Not sure if it's related, but I started having a lot of "ERROR"s during uploads (and even when it works, it will be very slow) after upgrading from 1.21 to 2.02beta. It will eventually work if I repeat the upload.

    That's interesting. Did you upgrade DuetWiFiServer at the same time, or were you already using version 1.21? Does M122 still report a good signal strength?

    I went from FW 1.21 / DWC ???? / WiFi FW ???? to FW 2.02beta1 / DWC .122.1 / WiFi FW 1.21 installing all at once. Then I went from that to FW 2.02RC1 / DWC 1.22.3, also both at the same time.

    Errors are occuring with the last one (2.02RC1), didn't seem to be as much with the previous one (2.02beta1) but I cannot be sure as I printed very little with that one. Also, the speed is very low, most of the time about 50-60kb/s, with sparse peaks of 150kb/s.

    Wifi setup is the same as always, I think it is ok. It's a Ubiquity UniFi inside the same room as the printer and the laptop. Signal should be very strong. M122 reports:

    Network state is running
    WiFi module is connected to access point
    Failed messages: pending 0, notready 0, noresp 0
    WiFi firmware version 1.21
    WiFi MAC address 5c:cf:7f:76:6d:47
    WiFi Vcc 3.32, reset reason Turned on by main processor
    WiFi flash size 4194304, free heap 14928
    WiFi IP address 192.168.47.144
    WiFi signal strength -41dBm, reconnections 0, sleep mode modem
    Socket states: 0 0 0 0 0 0 0 0


  • administrators

    You might have a strong signal but also strong interference. Have you tried setting your router to a different wireless channel?


 

Looks like your connection to Duet3D was lost, please wait while we try to reconnect.