DWC2 Uploading large Gcode files results in network error



  • I seem to be unable to upload larger >3 MB with DWC2, I always get a network error.
    I have no issues uploading the same file when I revert to DWC1.

    I'm running 2.05 (just went from 2.04 in case that was the problem) but I have the same issues.
    I know the wifi signal strength is on the 'low' side, but if I have no issues uploading in DWC1, then why can't I upload with DWC2?

    Board: Duet WiFi 1.0 or 1.01
    Firmware: RepRapFirmware for Duet 2 WiFi/Ethernet 2.05 (2019-12-13b1)
    Duet WiFi Server Version: 1.23

    M122
    === Diagnostics ===
    RepRapFirmware for Duet 2 WiFi/Ethernet version 2.05 running on Duet WiFi 1.0 or 1.01
    Board ID: 08DAM-999TL-MQ4S8-6J1FL-3SN6S-9QBRX
    Used output buffers: 1 of 24 (10 max)
    === RTOS ===
    Static ram: 25712
    Dynamic ram: 92696 of which 304 recycled
    Exception stack ram used: 272
    Never used ram: 12088
    Tasks: NETWORK(ready,628) HEAT(blocked,1232) MAIN(running,3800) IDLE(ready,160)
    Owned mutexes:
    === Platform ===
    Last reset 00:07:28 ago, cause: software
    Last software reset at 2020-01-08 11:06, reason: User, spinning module GCodes, available RAM 12396 bytes (slot 2)
    Software reset code 0x0003 HFSR 0x00000000 CFSR 0x00000000 ICSR 0x0441f000 BFAR 0xe000ed38 SP 0xffffffff Task 0x4e49414d
    Error status: 0
    Free file entries: 10
    SD card 0 detected, interface speed: 12.0MBytes/sec
    SD card longest block write time: 166.0ms, max retries 0
    MCU temperature: min 32.0, current 32.6, max 34.0
    Supply voltage: min 12.7, current 12.8, max 13.0, 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
    Date/time: 2020-01-09 10:32:44
    Cache data hit count 1403011763
    Slowest loop: 53.11ms; fastest: 0.06ms
    I2C nak errors 0, send timeouts 0, receive timeouts 0, finishTimeouts 0, resets 0
    === Move ===
    Hiccups: 0, FreeDm: 160, MinFreeDm: 160, MaxWait: 0ms
    Bed compensation in use: none, comp offset 0.000
    === DDARing ===
    Scheduled moves: 0, completed moves: 0, StepErrors: 0, LaErrors: 0, Underruns: 0, 0
    === Heat ===
    Bed heaters = 0 -1 -1 -1, chamberHeaters = 2 -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: 189.51ms; 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.23
    WiFi MAC address 5c:cf:7f:2b:eb:38
    WiFi Vcc 3.38, reset reason Turned on by main processor
    WiFi flash size 4194304, free heap 25936
    WiFi IP address 192.168.0.56
    WiFi signal strength -67dBm, reconnections 0, sleep mode modem
    Socket states: 0 0 0 0 0 0 0 0
    

    I saw that in the above M122, the SD card longest block write time: 166.0ms is pretty long, but I did a few subsequent M122 and the longest block write time is 0ms


  • administrators

    Please try to upgrade to DWC 2.0.5. The new version no longer relies on the "axios" library for HTTP calls but uses native AJAX calls instead, so I hope this will solve your problem.


  • administrators

    @jrjones88 said in DWC2 Uploading large Gcode files results in network error:

    but I did a few subsequent M122 and the longest block write time is 0ms

    That just means you haven't written to the SD card between sending the previous M122 command and the current one.



  • Hello,
    I have the same problem, DUET WIFI RRF 3.0 and DWC 2.0.6.
    Unable to upload large files from both the web and CURA, I have to go back to DWC1.


  • administrators

    @danzaywer What browser are you using and what is the error message you get?


  • administrators

    @danzaywer said in DWC2 Uploading large Gcode files results in network error:

    Hello,
    I have the same problem, DUET WIFI RRF 3.0 and DWC 2.0.6.
    Unable to upload large files from both the web and CURA, I have to go back to DWC1.

    Please check (using M122) that you are running version 1.23 of the WiFi module firmware.



  • @dc42

    • WiFi -
      Network state is running
      WiFi module is connected to access point
      Failed messages: pending 0, notready 0, noresp 1
      WiFi firmware version 1.23
      WiFi MAC address 80:7d:3a:3f:f5:64
      WiFi Vcc 3.42, reset reason Turned on by main processor
      WiFi flash size 4194304, free heap 18600
      WiFi IP address 192.168.101.136
      WiFi signal strength -57dBm, reconnections 0, sleep mode modem
      Socket states: 2 2 0 0 0 0 0 0


  • @chrishamm

    I tried both with chrome and with edge
    browser give me this:
    upload error.png
    CURA give me this:
    upload error 2.png


  • administrators

    Both error messages mean that the connection is interrupted while an upload is in progress. You can try to change your WiFi channel and check if that makes a difference. Also, if you can, move your printer closer to your WiFi access point and check if you can upload files then.

    This guide may give you further hints on how to resolve this problem.



  • Thank you,
    in the evening I will carry out checks on the channel. The printer is a fair distance from the access point.
    With the current situation and DWC1 I have no problem and the upload is very fast.


  • administrators

    Are you able to get a WireShark trace of a failed upload? That might help us diagnose the problem.



  • @dc42
    I can try



  • @chrishamm
    @dc42
    Ok, I changed the channel but it didn't help, I moved the printer 1 meter sideways and now I can upload a 30 MB file without errors. I intend to restore the previous position and analyze with wireshark to understand the cause of the problem, the printer is about 5 meters from an ubiquiti mounted on the ceiling without obstacles, in both positions.
    Thanks for the support, as soon as I have the wireshark trace I will upload it.



  • @chrishamm said in DWC2 Uploading large Gcode files results in network error:

    Please try to upgrade to DWC 2.0.5. The new version no longer relies on the "axios" library for HTTP calls but uses native AJAX calls instead, so I hope this will solve your problem.

    I've haven't been able to test it for a while, but I've since upgraded to 2.0.7 and while I do have a higher success rate, the odd time the upload still fails.

    I've attached 3 wireshark traces of failed uploads here: https://1drv.ms/u/s!AgTPtiCYHi3hh8oNZ5d6wYz7VkdVzQ?e=pKpMUd



  • @danzaywer said in DWC2 Uploading large Gcode files results in network error:

    I moved the printer 1 meter sideways

    Welcome to the vaugeries of wireless.


Log in to reply