• Tags
  • Documentation
  • Order
  • Register
  • Login
Duet3D Logo Duet3D
  • Tags
  • Documentation
  • Order
  • Register
  • Login

Slow Upload speeds using Web Interface

Scheduled Pinned Locked Moved
General Discussion
6
15
635
Loading More Posts
  • Oldest to Newest
  • Newest to Oldest
  • Most Votes
Reply
  • Reply as topic
Log in to reply
This topic has been deleted. Only users with topic management privileges can see it.
  • undefined
    jay_s_uk @MCRikki
    last edited by 16 Nov 2022, 14:41

    @MCRikki upload it to system

    Owns various duet boards and is the main wiki maintainer for the Teamgloomy LPC/STM32 port of RRF. Assume I'm running whatever the latest beta/stable build is

    1 Reply Last reply Reply Quote 0
    • undefined
      MCRikki @Phaedrux
      last edited by 16 Nov 2022, 19:39

      @Phaedrux Replaced the SD Card and still having the same issue. Went with a Class 10 card. The weird part is that downloads are going at a normal speed (about 200kb/s). And when I try to push an upload to it, it starts around 150kb/s, and then just tanks down to about 12kb/s. It has a good connection to the access point, as the AP is right next to it.

      undefined 1 Reply Last reply 17 Nov 2022, 07:58 Reply Quote 0
      • undefined
        Phaedrux Moderator
        last edited by 16 Nov 2022, 21:22

        To eliminate the access point as a possible issue, can you test the Duet in Access Point mode, where it creates its own network that you connect to directly?

        https://docs.duet3d.com/en/User_manual/Reference/Gcodes#m589-configure-access-point-parameters

        Z-Bot CoreXY Build | Thingiverse Profile

        1 Reply Last reply Reply Quote 0
        • undefined
          dc42 administrators @MCRikki
          last edited by 17 Nov 2022, 07:58

          @MCRikki to see whether the network speed or the SD card writing speed is the problem, run these tests:

          1. Send M122 P104 to test the SD card write speed. You can if you wish add another parameter to specify the file size.

          2. Take a copy of one of your large GCode files, rename it to end with ".dummy" and upload it, looking at the reported upload speed just before it completes. The file will be uploaded to the Duet but not written to the SD card.

          Duet WiFi hardware designer and firmware engineer
          Please do not ask me for Duet support via PM or email, use the forum
          http://www.escher3d.com, https://miscsolutions.wordpress.com

          undefined 1 Reply Last reply 26 Feb 2024, 17:48 Reply Quote 0
          • undefined
            Yapeng、 @dc42
            last edited by Yapeng、 26 Feb 2024, 17:48

            @dc42
            I'm having the same problem, duet 2wifi, it's been going on for a long time and I've tried a lot of things to no avail, so I saw your reply here today so I thought I'd ask again. I prepared a 12mb file and changed it to .dummy and on the first two seconds the upload speed was 200kb/s then immediately went to 10kb/s then to 1-2kb/s. I've changed many class 10 memory cards and all new ones from sandisk, every time the same upload speed is only 1kb/s and the motherboard is right next to my router 0.5m with no cover in between. I've tried many versions of firmware and flashed the motherboard but still have the problem.

            m122
            === Diagnostics ===
            RepRapFirmware for Duet 2 WiFi/Ethernet version 3.3 (2021-06-15 21:44:54) running on Duet WiFi 1.02 or later + DueX5
            Board ID: 0JD0M-9P61A-J8PS8-6JTD6-3SJ6L-TUSGU
            Used output buffers: 3 of 24 (13 max)
            === RTOS ===
            Static ram: 23876
            Dynamic ram: 75820 of which 12 recycled
            Never used RAM 14708, free system stack 176 words
            Tasks: NETWORK(notifyWait,14.0%,244) HEAT(delaying,0.0%,330) Move(notifyWait,0.1%,319) DUEX(notifyWait,0.0%,24) MAIN(running,85.8%,413) IDLE(ready,0.1%,29), total 100.0%
            Owned mutexes: WiFi(NETWORK)
            === Platform ===
            Last reset 00:12:17 ago, cause: power up
            Last software reset at 2024-02-25 23:34, reason: User, GCodes spinning, available RAM 14708, slot 2
            Software reset code 0x0003 HFSR 0x00000000 CFSR 0x00000000 ICSR 0x0041f000 BFAR 0xe000ed38 SP 0x00000000 Task MAIN Freestk 0 n/a
            Error status: 0x00
            Aux0 errors 0,0,0
            Step timer max interval 0
            MCU temperature: min 32.7, current 39.2, max 39.7
            Supply voltage: min 24.1, current 24.2, max 24.4, under voltage events: 0, over voltage events: 0, power good: yes
            Heap OK, handles allocated/used 0/0, heap memory allocated/used/recyclable 0/0/0, gc cycles 0
            Driver 0: position 0, standstill, SG min/max not available
            Driver 1: position 0, standstill, SG min/max not available
            Driver 2: position 0, standstill, SG min/max not available
            Driver 3: position 0, standstill, SG min/max not available
            Driver 4: position 0, standstill, SG min/max not available
            Driver 5: position 0, standstill, SG min/max not available
            Driver 6: position 0, standstill, SG min/max not available
            Driver 7: position 0, standstill, SG min/max not available
            Driver 8: position 0, standstill, SG min/max not available
            Driver 9: position 0, standstill, SG min/max not available
            Driver 10: position 0
            Driver 11: position 0
            Date/time: 2024-02-26 18:39:18
            Cache data hit count 4294967295
            Slowest loop: 8.41ms; fastest: 0.17ms
            I2C nak errors 0, send timeouts 0, receive timeouts 0, finishTimeouts 0, resets 0
            === Storage ===
            Free file entries: 10
            SD card 0 detected, interface speed: 20.0MBytes/sec
            SD card longest read time 0.9ms, write time 6.7ms, max retries 0
            === Move ===
            DMs created 83, maxWait 0ms, bed compensation in use: none, comp offset 0.000
            === MainDDARing ===
            Scheduled moves 0, completed moves 0, hiccups 0, stepErrors 0, LaErrors 0, Underruns [0, 0, 0], CDDA state -1
            === AuxDDARing ===
            Scheduled moves 0, completed moves 0, hiccups 0, stepErrors 0, LaErrors 0, Underruns [0, 0, 0], CDDA state -1
            === Heat ===
            Bed heaters = 0 -1 -1 -1, chamberHeaters = -1 -1 -1 -1
            Heater 1 is on, I-accum = 0.0
            === GCodes ===
            Segments left: 0
            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
            USB is idle in state(s) 0
            Aux is idle in state(s) 0
            Trigger is idle in state(s) 0
            Queue is idle in state(s) 0
            LCD is idle in state(s) 0
            Daemon is idle in state(s) 0
            Autopause is idle in state(s) 0
            Code queue is empty.
            === DueX ===
            Read count 1, 0.08 reads/min
            === Network ===
            Slowest loop: 72.81ms; fastest: 0.00ms
            Responder states: HTTP(0) HTTP(0) HTTP(0) HTTP(0) FTP(0) Telnet(0), 0 sessions
            HTTP sessions: 1 of 8

            • WiFi -
              Network state is active
              WiFi module is connected to access point
              Failed messages: pending 0, notready 0, noresp 0
              WiFi firmware version 1.21RC2
              WiFi MAC address 10:5:eyeglasses: 👓 👓 ..........
              WiFi Vcc 3.34, reset reason Turned on by main processor
              WiFi flash size 4194304, free heap 12168
              WiFi IP address 192.16👓 👓 👓 👓 👓 ........
              WiFi signal strength -43dBm, mode none, reconnections 0, sleep mode modem
              Clock register ffffffff
              Socket states: 4 0 0 0 0 0 0 0

            m122 P104
            2024/2/26 18:41:13 SD read speed for 10.0Mbyte file was 1.42Mbytes/sec
            2024/2/26 18:41:05 SD write speed for 10.0Mbyte file was 3.33Mbytes/sec
            Testing SD card read speed...
            2024/2/26 18:41:03 m122 P104
            Testing SD card write speed...

            If you need any more information please talk to me, I would very much like you to help me with this long-standing problem. Thank you!

            undefined 1 Reply Last reply 26 Feb 2024, 17:50 Reply Quote 0
            • undefined
              jay_s_uk @Yapeng、
              last edited by 26 Feb 2024, 17:50

              @Yapeng maybe update the RRF and WiFi firmware versions to the latest ones. 3.3 and 1.21 are old now

              Owns various duet boards and is the main wiki maintainer for the Teamgloomy LPC/STM32 port of RRF. Assume I'm running whatever the latest beta/stable build is

              undefined 1 Reply Last reply 26 Feb 2024, 18:04 Reply Quote 0
              • undefined
                Yapeng、 @jay_s_uk
                last edited by Yapeng、 26 Feb 2024, 18:04

                @jay_s_uk
                Thanks so much for the advice, I've upgraded but the problem persists!
                I also tried uploading a gcode file of less than 1mb, and although the speed was still only 1kb/s, I found that when it showed uploading to 100%, it started uploading from 1% again and by then the speed had dropped to 500b/s. Then after a few tens of seconds it showed that the upload had failed! I have not been able to use my printer for a long time because this motherboard has not been able to upload my files, It used to work fine and to my great satisfaction, I don't know why all of a sudden it started not uploading files!

                m122
                === Diagnostics ===
                RepRapFirmware for Duet 2 WiFi/Ethernet version 3.4.6 (2023-07-21 14:08:28) running on Duet WiFi 1.02 or later + DueX5
                Board ID: 0JD0M-9P61A-J8PS8-6JTD6-3SJ6L-TUSGU
                Used output buffers: 1 of 26 (12 max)
                === RTOS ===
                Static ram: 23896
                Dynamic ram: 75728 of which 144 recycled
                Never used RAM 12312, free system stack 184 words
                Tasks: NETWORK(ready,12.1%,246) HEAT(notifyWait,0.0%,333) Move(notifyWait,0.0%,363) DUEX(notifyWait,0.0%,24) MAIN(running,85.1%,408) IDLE(ready,2.7%,30), total 100.0%
                Owned mutexes: WiFi(NETWORK)
                === Platform ===
                Last reset 00:00:27 ago, cause: software
                Last software reset at 2024-02-25 23:34, reason: User, GCodes spinning, available RAM 14708, slot 2
                Software reset code 0x0003 HFSR 0x00000000 CFSR 0x00000000 ICSR 0x0041f000 BFAR 0xe000ed38 SP 0x00000000 Task MAIN Freestk 0 n/a
                Error status: 0x00
                Aux0 errors 0,0,0
                Step timer max interval 0
                MCU temperature: min 39.1, current 39.9, max 40.1
                Supply voltage: min 24.1, current 24.2, max 24.4, under voltage events: 0, over voltage events: 0, power good: yes
                Heap OK, handles allocated/used 0/0, heap memory allocated/used/recyclable 0/0/0, gc cycles 0
                Events: 0 queued, 0 completed
                Driver 0: standstill, SG min n/a
                Driver 1: standstill, SG min n/a
                Driver 2: standstill, SG min n/a
                Driver 3: standstill, SG min n/a
                Driver 4: standstill, SG min n/a
                Driver 5: standstill, SG min n/a
                Driver 6: standstill, SG min n/a
                Driver 7: standstill, SG min n/a
                Driver 8: standstill, SG min n/a
                Driver 9: standstill, SG min n/a
                Driver 10:
                Driver 11:
                Date/time: 2024-02-26 19:00:21
                Cache data hit count 991818318
                Slowest loop: 6.39ms; fastest: 0.18ms
                I2C nak errors 0, send timeouts 0, receive timeouts 0, finishTimeouts 0, resets 0
                === Storage ===
                Free file entries: 10
                SD card 0 detected, interface speed: 20.0MBytes/sec
                SD card longest read time 2.3ms, write time 0.0ms, max retries 0
                === Move ===
                DMs created 83, segments created 0, maxWait 0ms, bed compensation in use: none, comp offset 0.000
                === MainDDARing ===
                Scheduled moves 0, completed 0, hiccups 0, stepErrors 0, LaErrors 0, Underruns [0, 0, 0], CDDA state -1
                === AuxDDARing ===
                Scheduled moves 0, completed 0, hiccups 0, stepErrors 0, LaErrors 0, Underruns [0, 0, 0], CDDA state -1
                === Heat ===
                Bed heaters 0 -1 -1 -1, chamber heaters -1 -1 -1 -1, ordering errs 0
                Heater 1 is on, I-accum = 0.0
                === GCodes ===
                Segments left: 0
                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
                USB is idle in state(s) 0
                Aux is idle in state(s) 0
                Trigger is idle in state(s) 0
                Queue is idle in state(s) 0
                LCD is idle in state(s) 0
                Daemon is idle in state(s) 0
                Autopause is idle in state(s) 0
                Code queue is empty
                === DueX ===
                Read count 1, 2.20 reads/min
                === Network ===
                Slowest loop: 62.05ms; fastest: 0.00ms
                Responder states: HTTP(0) HTTP(0) HTTP(0) HTTP(0) FTP(0) Telnet(0)
                HTTP sessions: 1 of 8
                = WiFi =
                Interface state: active
                Module is connected to access point
                Failed messages: pending 0, notready 0, noresp 0
                WiFi firmware version 1.27
                WiFi MAC address 10:5: 👓 👓 👓
                WiFi Vcc 3.34, reset reason Turned on by main processor
                WiFi flash size 4194304, free heap 21976
                WiFi IP address 192.16👓 👓 👓
                WiFi signal strength -35dBm, mode 802.11n, reconnections 0, sleep mode modem
                Clock register 00002002
                Socket states: 0 0 0 0 0 0 0 0

                droftartsundefined undefined 2 Replies Last reply 26 Feb 2024, 19:14 Reply Quote 0
                • T3P3Tonyundefined T3P3Tony referenced this topic 26 Feb 2024, 18:40
                • droftartsundefined
                  droftarts administrators @Yapeng、
                  last edited by 26 Feb 2024, 19:14

                  @Yapeng check your SD card for free space and possibly other problems: see https://docs.duet3d.com/en/User_manual/RepRapFirmware/SD_card#troubleshooting-sd-card-issues

                  If in doubt, replace the SD card for a higher performance one. See our recommendation here: https://docs.duet3d.com/en/User_manual/RepRapFirmware/SD_card#specification

                  Ian

                  Bed-slinger - Mini5+ WiFi/1LC | RRP Fisher v1 - D2 WiFi | Polargraph - D2 WiFi | TronXY X5S - 6HC/Roto | CNC router - 6HC | Tractus3D T1250 - D2 Eth

                  undefined 1 Reply Last reply 26 Feb 2024, 21:17 Reply Quote 0
                  • undefined
                    Yapeng、 @droftarts
                    last edited by 26 Feb 2024, 21:17

                    @droftarts thanks, I've changed many class 10 memory cards and all new ones from sandisk, every time the same upload speed is only 1kb/s and the motherboard is right next to my router 0.5m with no cover in between. I've tried many versions of firmware and flashed the motherboard but still have the problem.

                    1 Reply Last reply Reply Quote 0
                    • undefined
                      dc42 administrators @Yapeng、
                      last edited by 26 Feb 2024, 21:33

                      @Yapeng the slow upload when you change the file extension to .dummy indicates that the issue is nothing to do with the SD card.

                      My guess is that there is an incompatibility between WiFi module on the Duet and your WiFi router/access point. Here are some things you can try:

                      • Try upgrading the WiFi module firmware to 2.1beta6 from https://github.com/Duet3D/WiFiSocketServerRTOS/releases/tag/2.1beta6
                      • Try a different router/access point
                      • Check which channel your router/access point is using. You router WiFi configuration or status page may tell you, if it doesn't then use a WiFi scanner app on a smartphone. If it's operating on channel 1 then change it to a different channel, e.g. 7 or 11.

                      Duet WiFi hardware designer and firmware engineer
                      Please do not ask me for Duet support via PM or email, use the forum
                      http://www.escher3d.com, https://miscsolutions.wordpress.com

                      1 Reply Last reply Reply Quote 0
                      • First post
                        Last post
                      Unless otherwise noted, all forum content is licensed under CC-BY-SA